AIsa Web Search & Research

post_exa_contents

Destructive

Fetch page text and metadata for URLs you already have. ids is required and takes the id values from post_exa_search — which are plain URLs, so any URL works. Toggle text, highlights, summary, subpages and livecrawl. Returns results[] with id, title, url, author and text, plus a statuses[] array giving per-URL status and source — read it, because a URL that could not be fetched is reported there rather than raising. Cached results are served instantly; a miss falls back to a live crawl. Measured at 1.2 seconds. Use current endpoint pricing and a fresh quote for this request. For a whole site rather than a URL list, post_firecrawl_crawl.

Usage-based billing; Default request estimate: $0.002 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "post_exa_contents"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 19, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / body

Added value: +{
+  "properties": {
+    "highlights": {
+      "description": "Return highlighted relevant snippets.",
+      "type": "boolean"
+    },
+    "ids": {
+      "description": "The URLs (or Exa result ids) to fetch contents for.",
+      "example": [
+        "https://example.com/article"
+      ],
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "livecrawl": {
+      "description": "Freshness policy: always live-crawl, fall back to live crawl on cache miss, or never live-crawl.",
+      "enum": [
+        "always",
+        "fallback",
+        "never"
+      ],
+      "type": "string"
+    },
+    "stream": {
+      "default": false,
+      "enum": [
+        false
+      ],
+      "type": "boolean"
+    },
+    "subpages": {
+      "description": "Number of linked subpages to also fetch.",
+      "type": "integer"
+    },
+    "summary": {
+      "description": "Return an AI-generated summary of the page.",
+      "type": "boolean"
+    },
+    "text": {
+      "description": "Return the full page text.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ids"
+  ],
+  "type": "object"
+}

removedInput schema / properties / highlights

Removed value: -{
-  "description": "Return highlighted relevant snippets.",
-  "type": "boolean"
-}

removedInput schema / properties / ids

Removed value: -{
-  "description": "The URLs (or Exa result ids) to fetch contents for.",
-  "example": [
-    "https://example.com/article"
-  ],
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / livecrawl

Removed value: -{
-  "description": "Freshness policy: always live-crawl, fall back to live crawl on cache miss, or never live-crawl.",
-  "enum": [
-    "always",
-    "fallback",
-    "never"
-  ],
-  "type": "string"
-}

removedInput schema / properties / stream

Removed value: -{
-  "default": false,
-  "enum": [
-    false
-  ],
-  "type": "boolean"
-}

removedInput schema / properties / subpages

Removed value: -{
-  "description": "Number of linked subpages to also fetch.",
-  "type": "integer"
-}

removedInput schema / properties / summary

Removed value: -{
-  "description": "Return an AI-generated summary of the page.",
-  "type": "boolean"
-}

removedInput schema / properties / text

Removed value: -{
-  "description": "Return the full page text.",
-  "type": "boolean"
-}

changedInput schema / required

Previous value: -[
-  "ids"
-]New value: +[
+  "body"
+]

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / stream

Added value: +{
+  "default": false,
+  "enum": [
+    false
+  ],
+  "type": "boolean"
+}

Changed1 schema field changedOct 15, 2026

removedInput schema / properties / stream

Removed value: -{
-  "default": false,
-  "enum": [
-    false
-  ],
-  "type": "boolean"
-}

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / stream

Added value: +{
+  "default": false,
+  "enum": [
+    false
+  ],
+  "type": "boolean"
+}

First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds real context beyond the annotations: cache-hit vs. live-crawl fallback semantics, a measured latency figure, and the important failure-mode disclosure that unfetchable URLs surface in `statuses[]` instead of raising. It does not, however, reconcile the surprising destructiveHint=true / readOnlyHint=false annotations for what is nominally a fetch operation, which would have been valuable.

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

Conciseness4/5

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

Front-loaded with purpose and the required parameter, then behavior, then the sibling alternative. The trailing pricing sentences ('Use current endpoint pricing and a fresh quote') and the injected pricing block are boilerplate that dilutes an otherwise tight description.

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

Completeness4/5

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

For a nested-schema fetch tool with an output schema, the description covers what matters: inputs, cache/livecrawl behavior, and the non-obvious `statuses[]` error channel. Return-field detail slightly duplicates the output schema, but the failure-mode explanation is genuinely additive.

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

Parameters4/5

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

Reported schema coverage is 0% at the top level (the `body` wrapper is undescribed), so the description carries the burden and does it well: it names `ids` as required, explains its origin and format, and enumerates the `text`, `highlights`, `summary`, `subpages` and `livecrawl` toggles in prose.

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

Purpose5/5

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

Opens with a precise verb+resource+scope: 'Fetch page text and metadata for URLs you already have.' It explicitly positions itself relative to post_exa_search (source of the `id` values) and post_firecrawl_crawl (whole-site alternative), so an agent can distinguish it from siblings without opening a schema.

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

Usage Guidelines5/5

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

States the precondition ('URLs you already have', `ids` required) and clarifies that ids are plain URLs so any URL works. It also names the alternative and the condition that selects it: 'For a whole site rather than a URL list, post_firecrawl_crawl.'

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

All AIsa Web Search & Research tools Inspect

Try in Browser