AnyAPI

Browse APIs

list_apis

Read-only

Browse available AnyAPI APIs as lightweight summaries (id, name, category, USD pricing), optionally filtered by category. Descriptions and schemas are omitted to keep catalog responses small. Each pricing offer carries both maxUsd (billed per request) and maxPer1kUsd (the same price per 1,000 requests).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes	Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking.
`category`	No	optional category slug to filter by

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scrapers`	Yes	matching APIs (lightweight summaries: no description or schemas)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / context / description

Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking."

Changed1 schema field changedSep 14, 2026

addedOutput schema / properties / scrapers / items / properties / pricing / properties / from / properties / addons

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "usd": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "id",
+      "label",
+      "field",
+      "usd"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed17 schema fields changedSep 3, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

removedInput schema / properties / query

Removed value: -{
-  "description": "optional free-text filter over API name and description",
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

removedOutput schema / properties / scrapers / items / properties / baseUsd

Removed value: -{
-  "description": "fixed cost per request in USD, charged regardless of count",
-  "type": "number"
-}

addedOutput schema / properties / scrapers / items / properties / excludesCallerDelay
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / scrapers / items / properties / execution

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "mode": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / scrapers / items / properties / failover
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / scrapers / items / properties / heavy / description

Removed value: -"true when this API's responses are typically large; pass fields, max_items, or summary to run_api (and a small limit in the input) to keep the result out of your context"

addedOutput schema / properties / scrapers / items / properties / method
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / scrapers / items / properties / path
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / scrapers / items / properties / perItemUnit

Removed value: -{
-  "description": "the unit perItemUsd is charged per: 'result' (default) or an input unit like 'username' for input-priced SKUs",
-  "type": "string"
-}

removedOutput schema / properties / scrapers / items / properties / perItemUsd

Removed value: -{
-  "description": "marginal cost in USD per billable unit (see perItemUnit); total = baseUsd + perItemUsd × unitCount, capped at priceUsd",
-  "type": "number"
-}

removedOutput schema / properties / scrapers / items / properties / priceUsd

Removed value: -{
-  "description": "maximum price per request in USD (the reserved ceiling at the default limit)",
-  "type": "number"
-}

addedOutput schema / properties / scrapers / items / properties / pricing

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "failoverMaxPer1kUsd": {
+      "type": "number"
+    },
+    "failoverMaxUsd": {
+      "type": "number"
+    },
+    "from": {
+      "additionalProperties": false,
+      "properties": {
+        "baseUsd": {
+          "type": [
+            "null",
+            "number"
+          ]
+        },
+        "maxPer1kUsd": {
+          "type": "number"
+        },
+        "maxUsd": {
+          "type": "number"
+        },
+        "model": {
+          "type": "string"
+        },
+        "perUnitUsd": {
+          "type": [
+            "null",
+            "number"
+          ]
+        },
+        "unit": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "model",
+        "unit",
+        "maxUsd",
+        "maxPer1kUsd"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "from",
+    "failoverMaxUsd",
+    "failoverMaxPer1kUsd"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / scrapers / items / properties / provider
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / scrapers / items / required

Previous value: -[
-  "id",
-  "slug",
-  "category",
-  "name",
-  "priceUsd",
-  "baseUsd",
-  "perItemUsd"
-]New value: +[
+  "id",
+  "slug",
+  "category",
+  "name",
+  "method",
+  "path",
+  "provider",
+  "execution",
+  "pricing",
+  "failover"
+]

Changed1 schema field changedJul 10, 2026

addedOutput schema / properties / scrapers / items / properties / heavy

Added value: +{
+  "description": "true when this API's responses are typically large; pass fields, max_items, or summary to run_api (and a small limit in the input) to keep the result out of your context",
+  "type": "boolean"
+}

Changed5 schema fields changedJun 24, 2026

changedOutput schema / properties / scrapers / description

Previous value: -"matching APIs"New value: +"matching APIs (lightweight summaries: no description or schemas)"

removedOutput schema / properties / scrapers / items / properties / description
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / scrapers / items / properties / inputSchema
```
Removed value: -{
-  "description": "normalized input JSON Schema"
-}
```
removedOutput schema / properties / scrapers / items / properties / outputSchema
```
Removed value: -{
-  "description": "normalized output JSON Schema"
-}
```

changedOutput schema / properties / scrapers / items / required

Previous value: -[
-  "id",
-  "slug",
-  "category",
-  "name",
-  "description",
-  "priceUsd",
-  "baseUsd",
-  "perItemUsd"
-]New value: +[
+  "id",
+  "slug",
+  "category",
+  "name",
+  "priceUsd",
+  "baseUsd",
+  "perItemUsd"
+]

First observedJun 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive behavior, so the description earns credit for going beyond them: it discloses the deliberate omission of descriptions/schemas to keep responses small, and explains the pricing semantics of maxUsd vs maxPer1kUsd. It does not address pagination or result-size limits for a catalog list, and the idempotentHint=false on a read tool is left unexplained.

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?

Three tight sentences: what it returns, what it deliberately withholds, and how to read the pricing fields. Front-loaded with the core purpose, and every sentence carries information the agent cannot get from the schema or annotations.

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?

With an output schema present, return-value documentation is not required, yet the description usefully pre-explains the pricing fields, and read-only annotations cover the safety profile. The only meaningful gap is sibling routing between list_apis, search_apis, and get_api, which the agent must infer.

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%, so the schema already documents both the required context parameter and the optional category slug. The description only restates the category filter as optional and adds nothing about slug formatting or valid values, making the baseline 3 appropriate.

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 names a specific verb and resource (browse/list APIs) and defines the exact shape of the result set — lightweight summaries with id, name, category, and USD pricing — which cleanly separates it from get_api (single-API detail) since it states descriptions and schemas are omitted. It does not, however, name or contrast with the search_apis sibling, which is the closest competing tool for discovery.

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

Usage Guidelines3/5

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

"optionally filtered by category" is an implied usage hint and gives the agent a sense of when the filter applies, but there is no explicit when-to-use guidance, no statement of when NOT to use it, and no routing to search_apis or get_api as alternatives. Usage must be inferred from the purpose sentence.

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

All AnyAPI tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?