Skip to main content
Glama

pdf_extract

Extract text from PDF files to access content for analysis, editing, or processing. Provide a PDF URL to retrieve text data.

Instructions

Extract text from a PDF file ($0.003)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPDF URL

Implementation Reference

  • index.js:33-33 (registration)
    Registration of the 'pdf_extract' tool in the TOOLS array.
    { name: 'pdf_extract', description: 'Extract text from a PDF file', inputSchema: { type: 'object', properties: { url: { type: 'string', description: 'PDF URL' } }, required: ['url'] }, endpoint: '/pdf/extract', price: '$0.003' },
  • index.js:50-79 (handler)
    Generic callTool function that dispatches the API request for all tools, including 'pdf_extract'.
    async function callTool(endpoint, params) {
      const fetch = (await import('node-fetch')).default;
      const isGet = ['GET'].includes((TOOLS.find(t => t.endpoint === endpoint) || {}).method);
      
      const url = isGet 
        ? `${BASE_URL}${endpoint}?${new URLSearchParams(params)}`
        : `${BASE_URL}${endpoint}`;
      
      const res = await fetch(url, {
        method: isGet ? 'GET' : 'POST',
        headers: {
          'Content-Type': 'application/json',
          'Authorization': `Bearer ${API_KEY}`,
        },
        body: isGet ? undefined : JSON.stringify(params),
      });
      
      const text = await res.text();
      let data;
      try { data = JSON.parse(text); } catch { data = { raw: text }; }
      
      if (!res.ok) {
        if (res.status === 402) {
          throw new Error(`Insufficient credits. Add credits at https://iteratools.com. Cost: ${TOOLS.find(t=>t.endpoint===endpoint)?.price || 'see docs'}`);
        }
        throw new Error(`API error ${res.status}: ${text.substring(0, 200)}`);
      }
      
      return data;
    }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It provides valuable cost information ('$0.003') not found elsewhere, but fails to disclose output format, file size limits, whether the operation is read-only, or error handling behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise with zero waste. The action ('Extract text from a PDF file') is front-loaded, and the pricing parenthetical is appropriately placed as metadata without obscuring the primary purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite being a simple single-parameter tool, the lack of output schema means the description should explain what gets returned (plain text? structured JSON? confidence scores?). It also omits file size limits and OCR capabilities, leaving significant gaps for an extraction tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% ('PDF URL'), so the baseline is 3. The description does not add semantic details beyond the schema, such as supported protocols, URL accessibility requirements, or examples of valid inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Extract') and resource ('text from a PDF file'), clearly distinguishing it from sibling 'pdf_generate'. However, it does not clarify whether it handles scanned PDFs via OCR (relevant to sibling 'image_ocr') or only text-based PDFs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this tool versus alternatives. Given siblings like 'image_ocr' (for scanned documents) and 'scrape' (for HTML content), the description should specify preferred use cases but does not.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredpsantos33/itera-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server