get_contents

Pack: exa · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/get_contents for the schema, then POST the same URL with its arguments for the data.

Retrieve clean, parsed page contents (text) for one or more Exa result IDs or URLs. Use after search to read the full content of pages. Example: get_contents({ ids: [“https://example.com/article”] })

Parameters

NameTypeRequiredDescription
idsstring,arrayyesAn Exa result ID or URL, or an array of them.
itemsstringno
_apiKeystringnoOptional — your own Exa API key for higher limits; omit to use the shared Pipeworx key.

Example call

Arguments

{
  "ids": "https://example.com/article"
}

curl

curl -X POST https://gateway.pipeworx.io/exa/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_contents","arguments":{"ids":"https://example.com/article"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('get_contents', {
  "ids": "https://example.com/article"
});

More examples

{
  "ids": [
    "https://example.com/article1",
    "https://example.com/article2"
  ]
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the exa pack
{
  "mcpServers": {
    "exa": {
      "url": "https://gateway.pipeworx.io/exa/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 17, 2026