---
title: "Adobe PDF Services"
description: "Request a PDF asset upload URL; Submit one PDF text/table extraction job; Read PDF extraction status and result links."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Adobe PDF Services

<p>Request a PDF asset upload URL; Submit one PDF text/table extraction job; Read PDF extraction status and result links.</p>

<details data-command-index><summary>What you can do (3)</summary>
<h2>What you can do</h2>
<p>Available commands: 3 (1 read, 2 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/adobe-pdf#command-adobe-pdf-assets-create">Request a PDF asset upload URL</a> — <code>adobe-pdf.assets.create</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/adobe-pdf#command-adobe-pdf-extract-create">Submit one PDF text/table extraction job</a> — <code>adobe-pdf.extract.create</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/adobe-pdf#command-adobe-pdf-extract-get">Read PDF extraction status and result links</a> — <code>adobe-pdf.extract.get</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/adobe-pdf">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Adobe PDF Services, then enter the issued values in the connection form below.</p>
<ol>
<li>Create PDF Services API credentials in Adobe Acrobat Services &gt; Get started / Adobe Developer Console and download the server-to-server client ID and client secret. Enter the two Adobe PDF Services fields; a Creative Cloud user password or browser token is not a substitute. Tooluse.net exchanges credentials for each explicit command. Request a PDF asset upload URL, then upload the PDF yourself with PUT to that returned uploadUri and Content-Type: application/pdf; keep the presigned URL private. Pass its assetID to Submit one PDF text/table extraction job. Submission may consume Adobe document transactions and applies Adobe file/page limits; select this write command only after checking the file and your plan quota. It returns jobId from the 201 Location header. Call the status command separately with that ID, then download content.downloadUri yourself if status is done. Tooluse.net does not upload arbitrary files, automatically poll, retry, or fetch presigned URLs. Large/complex PDF support and Adobe limits remain provider constraints, not a claim of arbitrary document processing.</li>
</ol>
<p><a href="https://developer.adobe.com/document-services/docs/overview/pdf-extract-api/gettingstarted/">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Adobe PDF Services client ID</td>
<td>Required</td>
</tr>
<tr>
<td>Adobe PDF Services client secret</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "path": {
      "jobId": "job-demo"
    }
  }
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-adobe-pdf-assets-create">
<summary><span>Request a PDF asset upload URL — <code>adobe-<wbr>pdf.<wbr>assets.<wbr>create</code></span></summary>
<p>Request a PDF asset upload URL. One explicit request/page; no automatic retries or pagination.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/adobe-pdf?command=adobe-pdf.assets.create">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>body.mediaType</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>const: &quot;application/pdf&quot;; minLength: 1; maxLength: 1000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/adobe-pdf/commands/adobe-pdf.assets.create">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "mediaType": "application/pdf"
  }
}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-adobe-pdf-extract-create">
<summary><span>Submit one PDF text/table extraction job — <code>adobe-<wbr>pdf.<wbr>extract.<wbr>create</code></span></summary>
<p>Submit one PDF text/table extraction job. One explicit request/page; no automatic retries or pagination.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/adobe-pdf?command=adobe-pdf.extract.create">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>body.assetID</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 300; pattern: &quot;^urn:aaid:[A-Za-z0-9:_-]+$&quot;</code></td>
</tr>
<tr>
<td><code>body.elementsToExtract</code></td>
<td>array</td>
<td>Required</td>
<td></td>
<td><code>minItems: 1; maxItems: 2; uniqueItems: true</code></td>
</tr>
<tr>
<td><code>body.elementsToExtract[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;text&quot;,&quot;tables&quot;]; minLength: 1; maxLength: 1000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/adobe-pdf/commands/adobe-pdf.extract.create">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "assetID": "urn:aaid:AS:US:asset-demo",
    "elementsToExtract": [
      "text",
      "tables"
    ]
  }
}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-adobe-pdf-extract-get">
<summary><span>Read PDF extraction status and result links — <code>adobe-<wbr>pdf.<wbr>extract.<wbr>get</code></span></summary>
<p>Read PDF extraction status and result links. One explicit request/page; no automatic retries or pagination.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/adobe-pdf?command=adobe-pdf.extract.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.jobId</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 1000; pattern: &quot;^[A-Za-z0-9_-]{1,200}$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/adobe-pdf/commands/adobe-pdf.extract.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "jobId": "job-demo"
  }
}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developer.adobe.com/document-services/docs/overview/pdf-extract-api/gettingstarted/">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/adobe-pdf/index.mdx