Skip to main content
Glama
Sign In

cloro

by dev.cloro
OverviewDiscussionsAdmin

Scrape Bing AI Mode

scrape_bing_aimode
Read-only

Submit a prompt to Bing AI Mode from a chosen country (and optionally US state) and return the answer text, cited sources and inline citation pills. Use this to see how Bing AI Mode answers a prompt and which brands/sources it mentions. Costs 6 credits (4 base + 2 sync surcharge); a state adds 2.

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": {
      "prompt": "<prompt>",
      "country": "<country>"
    },
    "name": "scrape_bing_aimode"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoOptional 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.
promptYesThe prompt to submit to Bing AI Mode. The maximum is 3,500 characters after URL encoding, so non-Latin scripts get fewer characters.
countryYesISO 3166-1 alpha-2 country code to geo-target the request from (e.g. "US"). Use list_countries to see supported codes per model.
includeNoOptional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (a CDN URL of the rendered Bing page). Leave unset for the leanest response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful cost behavior (6 credits = 4 base + 2 sync surcharge, +2 for a state) that is nowhere in the structured fields. It still says nothing about latency, failure modes, or what a partial/empty answer looks like.

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?

Two sentences, action-first, with the cost constraint compressed into a compact parenthetical. The second sentence overlaps somewhat with the first by restating what the tool reveals, so it is not perfectly waste-free.

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

Completeness3/5

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

With four parameters, a nested object and no output schema, the description does well to name the returned fields and the credit cost. Gaps remain around response shape specifics (how sources and citation pills are keyed), sync vs async behavior implied by the 'sync surcharge', and error handling for unsupported country/state combinations.

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 baseline is 3, but the description adds real meaning beyond the schema by tying the optional state parameter to a concrete price increase and by framing country/state as geo-targeting of the requester. It says nothing extra about the nested 'include' flags, though the schema already documents those thoroughly.

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?

States a specific verb and resource ('Submit a prompt to Bing AI Mode') and enumerates the return payload (answer text, cited sources, inline citation pills). Combined with the tool name, it is clearly distinguishable from siblings like scrape_google_ai_mode, scrape_chatgpt and scrape_gemini.

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?

Provides a concrete use case ('to see how Bing AI Mode answers a prompt and which brands/sources it mentions'), which tells an agent when this tool is the right one. It does not, however, explicitly contrast itself with the other AI-mode scrapers in the sibling list, so the choice between them is left implicit.

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

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