Skip to main content
Glama
Sign In
mcp-server-bing-webmaster

mcp-server-bing-webmaster

by isiahw1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_fetched_urls

Retrieve a list of URLs that Bing Webmaster Tools has fetched for your website to monitor indexing status and crawl activity.

Instructions

Get list of URLs that have been fetched.

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": {
      "site_url": "<site_url>"
    },
    "name": "get_fetched_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It only says 'Get list of URLs that have been fetched' and adds no context about pagination, auth, list scope, ordering, or whether the list represents all fetched URLs for the given site.

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?

The description is a single, front-loaded sentence with no wasted words. It is concise, though the brevity comes at the cost of missing useful context.

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

Completeness2/5

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

For a one-parameter tool with an output schema, the description provides only the bare minimum. It does not explain the meaning of site_url, the scope of 'fetched' URLs, or how this tool differs from the many related siblings, making it insufficient for confident selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description never mentions the site_url parameter or its relationship to the returned URLs. The tool description must compensate for the undocumented schema, but it does not.

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?

The description states a specific verb and resource: it returns a list of URLs that have been fetched. It is readable and clearly not a tautology, though it does not explicitly distinguish itself from siblings like get_fetched_url_details or explain what 'fetched' means in this domain.

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?

There is no guidance on when to use this tool versus any of the many sibling tools, nor any exclusionary context. The description only states what the tool does, leaving the agent to infer the appropriate call scenario.

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

Deploy Server

Other Tools