Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Bing crawl issues

bing_crawl_issues
Read-only

URLs Bingbot had problems crawling, with the HTTP code and issue type. Paged with offset and limit.

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": {
      "siteUrl": "<siteUrl>"
    },
    "name": "bing_crawl_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (1-500). Defaults to 50.
offsetNoNumber of items to skip, for paging. Defaults to 0.
siteUrlYesBing site URL exactly as bing_list_sites returns it, e.g. https://example.com/

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnly/non-destructive/closed-world, so the safety profile is covered. The description still adds real value by disclosing the returned fields (HTTP status code and issue type) and the paging behavior, which matters because there is no output schema. No mention of data freshness/window or result caps beyond the limit param.

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 short sentences, zero filler, with the resource definition front-loaded before the paging note. Every clause carries information an agent can use.

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?

For a simple three-parameter read tool with full schema coverage and annotations, this is close to sufficient. But with no output schema, the return shape is only sketched (HTTP code, issue type) — nothing about whether crawl timestamps, counts, or totals are included, so an agent can't fully anticipate the response.

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 three parameters are already documented including the siteUrl format hint pointing at bing_list_sites. The description's note about offset/limit paging only restates what the schema says, adding no new semantics. Baseline 3 applies.

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?

Names a specific resource (URLs Bingbot had problems crawling) plus the payload fields (HTTP code, issue type), which is far more informative than the title alone. It does not explicitly contrast itself with adjacent diagnostic siblings such as gsc_inspect_url or insights_index_audit, keeping it just short of a 5.

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

Usage Guidelines2/5

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

The description gives no guidance on when to reach for this tool versus alternatives — no mention of prerequisites (e.g., a verified site must exist via bing_list_sites), no exclusions, and no routing hints. Usage must be inferred entirely from the tool name and resource phrase.

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

All mowteng 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