Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get URL Submission Quota

bing_webmaster_get_url_submission_quota
Read-only

Check a site's remaining daily and monthly Bing URL submission quota before a large batch to avoid rejected submissions when the per-site cap is exceeded.

Instructions

How many URLs the site may still submit through bing_webmaster_submit_urls: today (daily_quota) and this month (monthly_quota). The quota is per site and Bing sets it by the site's age and standing, so it differs between sites. Check it before a large submission: Bing caps a batch at what is left, so a bigger one fails.

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": "<site>"
    },
    "name": "bing_webmaster_get_url_submission_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site, e.g. "example.com" or "https://www.example.com/". Matched against the sites this API key reaches (bing_webmaster_list_sites), tolerating a missing scheme, www. or trailing slash; an ambiguous or unknown site is refused with the list of accessible ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is a safe read (readOnlyHint=true, openWorldHint=true), so the description's job is to add context beyond that. It does: quota is per-site, set by site age and standing, varies across sites, and an oversized batch fails rather than partially succeeding. The only gap is no mention of what the response looks like on an unknown/ambiguous site, though the schema covers that.

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?

Three short sentences, each earning its place: what is returned, why values differ between sites, and the failure mode that motivates calling it first. The purpose and the payoff are front-loaded with no filler.

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 one-parameter read with no output schema, the description still names the returned fields and explains the quota's origin and cap behavior, which is enough to call it correctly. Minor omission: it does not say whether quota resets on a fixed schedule or describe the response shape beyond the two field names.

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 coverage is 100%, and the single site parameter is fully documented in the schema, including scheme/www/slash tolerance and the refusal behavior for ambiguous sites. The description only adds that quota is scoped per site, which is contextual rather than parameter-defining, so the baseline 3 applies.

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?

Names a specific resource (URL submission quota) and enumerates exactly what is returned: today's remaining submissions (daily_quota) and this month's (monthly_quota). It also distinguishes itself from the sibling it feeds into by naming bing_webmaster_submit_urls explicitly.

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?

Gives a concrete when-to-use rule: "Check it before a large submission," and pairs it with the sibling tool that consumes the result. It stops short of stating when the check is unnecessary (e.g. small batches), so it is clear context rather than full when/when-not guidance.

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