Skip to main content
Glama
Sign In
Bing Webmaster Tools MCP Server

Bing Webmaster Tools MCP Server

by parthguru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_url_submission_quota

Check your Bing URL submission quota and usage to see how many URLs you can still submit.

Instructions

Get information about URL submission quota and usage.

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_url_submission_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden. 'Get information' implies a read operation, but the description does not disclose quota semantics, reset windows, required permissions, or any other behavioral context an agent would need.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single short sentence, which is concise, but 'information about' adds little value. It is not bloated, yet it is under-specified rather than efficiently precise.

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?

The tool is simple and has an output schema, but the description still lacks enough context about quota and usage semantics, parameter expectations, and how this differs from related quota tools. It is minimally viable but not complete for an agent making an autonomous call.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the site_url parameter at all. The parameter name is somewhat self-explanatory, but the description adds no format, scope, or example to compensate for the schema gap.

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 ('Get') and resource ('URL submission quota and usage'), making the tool's basic purpose clear. It does not explicitly differentiate from sibling tools like get_content_submission_quota, so it loses a point.

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?

No guidance is given about when to use this tool versus alternatives, or what conditions make it the right choice. Sibling tools such as get_content_submission_quota and get_url_info overlap conceptually, but the description offers no routing hints.

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