API Plan Finder

Get recorded conditions of a plan or product

get_details

Read-onlyIdempotent

Use this when: you need every recorded condition, pricing rule and source sentence of one plan or product found by search or named by the user. Do not use this when: you want to compare plans against a workload (use search or check_conditions). Get every recorded condition for one API plan or product: value, which plans it applies to, exceptions, official source sentence, check date and purchase link. A product too long for one response comes with one source sentence per fact. Example: every recorded condition of 1 plan found by search.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`offer_id`	No	A plan id, e.g. "firecrawl-standard".
`product_id`	No	A product id, e.g. "firecrawl-api".

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	Yes
`offers`	Yes
`product`	Yes
`provider`	Yes
`link_notes`	No	The note of each link level (link.link_level) of the plans in this result, stated once.
`evidence_detail`	No	Present when the product was too long for one response: each fact carries one source sentence. Ask for a plan by offer_id for every sentence.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / offers / items / properties / plan_page

Added value: +{
+  "description": "The link to give the user with this plan, as a markdown link named \"<provider> <plan> — plan page\" (its pricing and sign-up page). The evidence sources under the conditions are for citing a condition.",
+  "type": "string"
+}

Changed12 schema fields changedOct 14, 2026
- addedOutput schema / properties / offers / items / properties / facts / items / properties / at_limit / properties / evidence / properties / source
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / offers / items / properties / facts / items / properties / at_limit / properties / evidence / properties / url
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / offers / items / properties / facts / items / properties / evidence / items / properties / source
```
Added value: +{
+  "description": "Official page the sentence was found on.",
+  "type": "string"
+}
```
- removedOutput schema / properties / offers / items / properties / facts / items / properties / evidence / items / properties / url
```
Removed value: -{
-  "description": "Official page the sentence was found on.",
-  "type": "string"
-}
```
- changedOutput schema / properties / offers / items / properties / facts / items / properties / evidence / items / required
```
Previous value: -[
-  "url",
-  "quote"
-]New value: +[
+  "source",
+  "quote"
+]
```
- changedOutput schema / properties / offers / items / properties / link / properties / provider_url / description
```
Previous value: -"The provider page itself, when url is this service's address that forwards to it."New value: +"The provider page itself. Only in a page made for a browser, where url is this service's address that forwards to it; MCP and REST results do not carry it."
```
- addedOutput schema / properties / offers / items / properties / link / properties / url / description
```
Added value: +"The only address to visit the plan: this service's /go/<offer_id>?r=<token> address, which forwards to the provider page. The token is made for this response and holds nothing about you."
```
- addedOutput schema / properties / product / properties / facts / items / properties / at_limit / properties / evidence / properties / source
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / product / properties / facts / items / properties / at_limit / properties / evidence / properties / url
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / product / properties / facts / items / properties / evidence / items / properties / source
```
Added value: +{
+  "description": "Official page the sentence was found on.",
+  "type": "string"
+}
```
- removedOutput schema / properties / product / properties / facts / items / properties / evidence / items / properties / url
```
Removed value: -{
-  "description": "Official page the sentence was found on.",
-  "type": "string"
-}
```
- changedOutput schema / properties / product / properties / facts / items / properties / evidence / items / required
```
Previous value: -[
-  "url",
-  "quote"
-]New value: +[
+  "source",
+  "quote"
+]
```

Changed4 schema fields changedOct 9, 2026

addedOutput schema / properties / offers / items / properties / facts / items / properties / at_limit

Added value: +{
+  "description": "Present for a plan with no automatic extra usage: what the official page says happens at the limit (kind no_extra_usage or restart_by_hand), with its sentence. With a workload that needs restarts, restarts gives their count, the price of each and the total, the numbers of monthly_cost.explanation.",
+  "properties": {
+    "evidence": {
+      "properties": {
+        "quote": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "kind": {
+      "enum": [
+        "no_extra_usage",
+        "restart_by_hand"
+      ]
+    },
+    "restarts": {
+      "properties": {
+        "count": {
+          "properties": {
+            "high": {
+              "type": "integer"
+            },
+            "low": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "total_usd": {
+          "properties": {
+            "high": {
+              "type": "number"
+            },
+            "low": {
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "usd_each": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "text": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "text",
+    "evidence"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / offers / items / properties / facts / items / properties / concurrency_unit

Added value: +{
+  "description": "get_details, concurrency only: the unit the page states the value in (unit, text such as \"100 threads\"). Against concurrent requests: equals_requests (value, text and the official line of the unit rule) when the unit rule counts this unit as requests, else note \"not the same unit as concurrent requests\"; \"unit not stated\" when the page names none.",
+  "type": "object"
+}

addedOutput schema / properties / product / properties / facts / items / properties / at_limit

Added value: +{
+  "description": "Present for a plan with no automatic extra usage: what the official page says happens at the limit (kind no_extra_usage or restart_by_hand), with its sentence. With a workload that needs restarts, restarts gives their count, the price of each and the total, the numbers of monthly_cost.explanation.",
+  "properties": {
+    "evidence": {
+      "properties": {
+        "quote": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "kind": {
+      "enum": [
+        "no_extra_usage",
+        "restart_by_hand"
+      ]
+    },
+    "restarts": {
+      "properties": {
+        "count": {
+          "properties": {
+            "high": {
+              "type": "integer"
+            },
+            "low": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "total_usd": {
+          "properties": {
+            "high": {
+              "type": "number"
+            },
+            "low": {
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "usd_each": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "text": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "text",
+    "evidence"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / product / properties / facts / items / properties / concurrency_unit

Added value: +{
+  "description": "get_details, concurrency only: the unit the page states the value in (unit, text such as \"100 threads\"). Against concurrent requests: equals_requests (value, text and the official line of the unit rule) when the unit rule counts this unit as requests, else note \"not the same unit as concurrent requests\"; \"unit not stated\" when the page names none.",
+  "type": "object"
+}

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / offers / items / properties / link / properties / provider_url

Added value: +{
+  "description": "The provider page itself, when url is this service's address that forwards to it.",
+  "type": "string"
+}

Changed2 schema fields changedOct 6, 2026

addedOutput schema / properties / link_notes

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "The note of each link level (link.link_level) of the plans in this result, stated once.",
+  "type": "object"
+}

removedOutput schema / properties / offers / items / properties / link / properties / note
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```

Changed2 schema fields changedOct 3, 2026

changedOutput schema / properties / offers / items / properties / facts / items / properties / applies_to / description

Previous value: -"get_details only: billing options the fact is limited to."New value: +"get_details only: billing options (billing) or search engines (search_engines) the fact is limited to."

changedOutput schema / properties / product / properties / facts / items / properties / applies_to / description

Previous value: -"get_details only: billing options the fact is limited to."New value: +"get_details only: billing options (billing) or search engines (search_engines) the fact is limited to."

First observedOct 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond that: the exact returned fields (value, applicable plans, exceptions, source sentence, check date, purchase link) and the truncation rule that a long product ships one source sentence per fact.

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

Conciseness3/5

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

Front-loaded appropriately with the when/when-not framing, but the phrase 'every recorded condition' recurs three times (when-clause, main sentence, example) and the example sentence restates the opening. The repetition dilutes an otherwise tight structure.

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 a full output schema and full annotation coverage, the description only needs to add selection and behavior context, which it largely does. It is complete enough to call correctly, though the input parameter contract is left entirely to the structured fields.

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% and the schema's own description already states 'Give exactly one of offer_id or product_id', so the required semantics are fully documented in structured data. The description only alludes to the input indirectly ('found by search or named by the user') without adding format or mutual-exclusion detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource (get every recorded condition, pricing rule and source sentence of one plan or product) and explicitly distinguishes itself from siblings by naming search and check_conditions for the comparison use case. An agent can tell it apart from check_conditions or cost_scenarios without opening any 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?

Uses an explicit 'Use this when / Do not use this when' pattern, names the alternative tools (search, check_conditions) for the excluded case, and gives a concrete example scenario. The routing decision is fully specified.

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

All API Plan Finder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?