Skip to main content
Glama
Sign In

CallAI SEO

by com.callaiapi
OverviewDiscussionsAdmin

Bing SERP

bing_serp
Read-only

Live Bing organic search results for a keyword in a given country and language: ranks, titles, URLs, snippets. Billed per call (about $0.002 for depth 10).

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": {
      "keyword": "<keyword>"
    },
    "name": "bing_serp"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoNumber of results to fetch, 10–100 (default 10). Cost grows with depth.
deviceNoDefault desktop.
keywordYesSearch query. Supports operators such as site:example.com.
language_codeNoLanguage code, e.g. en (default), de, fr, ja, es, pt, zh-CN.
location_codeNoDataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description only needs to add context — and it does, disclosing billing ('billed per call, about $0.002 for depth 10') and that results are live. It does not mention rate limits, failure modes, or that cost scales with depth beyond the schema note, which keeps it short of 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.

Conciseness5/5

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

Two sentences, purpose front-loaded, then the cost caveat — no filler. Every clause carries information an agent needs before calling.

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 read-only, single-call search tool with full schema coverage and no output schema, this is nearly complete: scope, result shape, and billing are all covered. The only soft spot is guidance on choosing Bing vs the google_serp sibling.

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 all five parameters (depth, device, keyword, language_code, location_code) are already documented in the schema. The description only restates the 'country and language' concept and the cost tie-in, adding little meaning beyond structured fields.

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?

Uses a specific verb+resource ('Live Bing organic search results for a keyword') and enumerates the returned fields (ranks, titles, URLs, snippets). The word 'Bing' implicitly separates it from the sibling google_serp, but the description never states the alternative explicitly.

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?

Intended usage (SERP/ranking research for a keyword in a country and language) is implied, and the per-call cost gives a reason to keep depth low. There is no explicit when-to-use vs google_serp guidance and no exclusions or preconditions.

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

All CallAI SEO 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