cloro

Scrape ChatGPT

scrape_chatgpt

Read-only

Submit a prompt to ChatGPT from a chosen country (and optionally US state) and return the full answer: text, cited sources, and optionally markdown, search queries, shopping results, and ads. Use this to see how ChatGPT answers a prompt and which brands/sources it mentions. Costs 7 credits (5 base + 2 sync surcharge); any of include.rawResponse, searchQueries, ads or shopping adds 2 once; include.productDetails adds 2 more; each prompt after the first adds 1; a state adds 2.

Input Schema

Name	Required	Description
`state`	No	Optional state code for state-level targeting (e.g. "CA" when country is "US"). Only some countries support this — call list_states for the supported countries and their codes.
`legacy`	No	Serve ChatGPT's desktop UI instead of the default mobile-web UI. Defaults to false.
`prompt`	Yes	The prompt to submit to ChatGPT, or an array of up to 5 prompts asked in order as follow-ups in the same conversation (1 extra credit per prompt after the first). An array returns an array of results, one per prompt.
`country`	Yes	ISO 3166-1 alpha-2 country code to geo-target the request from (e.g. "US"). Use list_countries to see supported codes per model.
`include`	No	Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML), rawResponse (the engine's unprocessed response payload), searchQueries (the web searches ChatGPT issued while answering), ads and shopping (sponsored and product results; ChatGPT tends to serve ads on follow-up prompts, so pass prompt as an array to see them), productDetails (the What to know summary and reviews of each product; needs shopping, and has no effect without it). Leave unset for the leanest response.
`disableWebSearch`	No	Stop cloro from forcing web search, to get the answer ChatGPT gives on its own. ChatGPT then searches only when it decides to, so expect empty sources, citationPills and searchQueries. Defaults to false (web search forced). Same cost.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / disableWebSearch / description

Added value: +"Stop cloro from forcing web search, to get the answer ChatGPT gives on its own. ChatGPT then searches only when it decides to, so expect empty sources, citationPills and searchQueries. Defaults to false (web search forced). Same cost."

changedInput schema / properties / include / description

Previous value: -"Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML), rawResponse (the engine's unprocessed response payload), searchQueries (the web searches ChatGPT issued while answering), ads and shopping (sponsored and product results; ChatGPT tends to serve ads on follow-up prompts, so pass prompt as an array to see them). Leave unset for the leanest response."New value: +"Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML), rawResponse (the engine's unprocessed response payload), searchQueries (the web searches ChatGPT issued while answering), ads and shopping (sponsored and product results; ChatGPT tends to serve ads on follow-up prompts, so pass prompt as an array to see them), productDetails (the What to know summary and reviews of each product; needs shopping, and has no effect without it). Leave unset for the leanest response."

Changed1 schema field changedOct 20, 2026
- addedInput schema / properties / include / properties / productDetails
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedOct 14, 2026

changedInput schema / properties / include / description

Previous value: -"Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML), rawResponse (the engine's unprocessed response payload), searchQueries (the web searches ChatGPT issued while answering), ads and shopping (sponsored and product results; these render only on the desktop UI, so pair them with legacy: true). Leave unset for the leanest response."New value: +"Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML), rawResponse (the engine's unprocessed response payload), searchQueries (the web searches ChatGPT issued while answering), ads and shopping (sponsored and product results; ChatGPT tends to serve ads on follow-up prompts, so pass prompt as an array to see them). Leave unset for the leanest response."

changedInput schema / properties / legacy / description

Previous value: -"Serve ChatGPT's desktop UI instead of the default mobile-web UI. Needed for include.ads and include.shopping, which only render on desktop. Defaults to false."New value: +"Serve ChatGPT's desktop UI instead of the default mobile-web UI. Defaults to false."

Changed5 schema fields changedOct 14, 2026

addedInput schema / properties / prompt / anyOf

Added value: +[
+  {
+    "maxLength": 10000,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "items": {
+      "maxLength": 10000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 5,
+    "minItems": 1,
+    "type": "array"
+  }
+]

changedInput schema / properties / prompt / description

Previous value: -"The prompt to submit to ChatGPT."New value: +"The prompt to submit to ChatGPT, or an array of up to 5 prompts asked in order as follow-ups in the same conversation (1 extra credit per prompt after the first). An array returns an array of results, one per prompt."

removedInput schema / properties / prompt / maxLength
```
Removed value: -10000
```
removedInput schema / properties / prompt / minLength
```
Removed value: -1
```
removedInput schema / properties / prompt / type
```
Removed value: -"string"
```

Changed1 schema field changedSep 2, 2026
- addedInput schema / properties / disableWebSearch
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedSep 2, 2026

changedInput schema / properties / include / description

Previous value: -"Optional flags to include heavier payload fields in the response. Leave unset for the leanest response."New value: +"Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML), rawResponse (the engine's unprocessed response payload), searchQueries (the web searches ChatGPT issued while answering), ads and shopping (sponsored and product results; these render only on the desktop UI, so pair them with legacy: true). Leave unset for the leanest response."

addedInput schema / properties / legacy / description

Added value: +"Serve ChatGPT's desktop UI instead of the default mobile-web UI. Needed for include.ads and include.shopping, which only render on desktop. Defaults to false."

Changed1 schema field changedAug 28, 2026
- addedInput schema / properties / legacy
```
Added value: +{
+  "type": "boolean"
+}
```
First observedAug 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already carry readOnly/openWorld/destructive=false, and the description adds a detailed credit-cost model (base, sync surcharge, per-feature add-ons, per-prompt and per-state increments) that an agent needs to judge cost. It also discloses that ads appear on follow-ups and that disableWebSearch changes source behavior. Lacks detail on response latency or failure modes, so not a 5.

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 return contents, followed by a compact cost sentence. The cost clause is dense but each part earns its place by conveying pricing that affects tool selection.

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 no output schema, the description correctly enumerates what comes back (text, cited sources, optional markdown/search queries/shopping/ads) and explains the cost and follow-up mechanics. Complete enough to invoke correctly; the only minor gap is not describing error/empty-result handling.

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?

Schema coverage is 100%, so the schema already documents parameters; the description nevertheless adds pricing semantics per parameter (productDetails adds 2, extra array prompts add 1, state adds 2) and reiterates subtle behavior (state needs list_states, disableWebSearch yields empty sources). Adds real value beyond the schema.

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?

Specific verb (submit a prompt) plus resource (ChatGPT) and explicit scope (geo-targeted by country/state), returning text, sources, and optional enriched fields. Clearly distinguishable from siblings like scrape_copilot and scrape_gemini by naming the model and the geo-targeting behavior.

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

Usage Guidelines4/5

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

States the intent explicitly: "Use this to see how ChatGPT answers a prompt and which brands/sources it mentions." It also points to list_countries and list_states for supported codes. It does not contrast with sibling scrapers, but the use case and auxiliaries are clear.

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

All cloro 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.

Scrape ChatGPT

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources