Skip to main content
Glama

bing_get_url_submission_quota

Check the remaining Bing URL submission quota for a site before submitting URLs, with a daily limit of 10,000 URLs per domain.

Instructions

Get the remaining URL submission quota for a site in Bing. Daily limit is 10,000 URLs per domain.

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

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It usefully discloses the daily cap of 10,000 URLs per domain and implies a non-mutating read, which is meaningful context, but it says nothing about reset timing, per-day vs. rolling window, or what the response contains.

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 with zero filler, and the core function is front-loaded ahead of the supporting quota detail. Nothing needs trimming.

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 simple one-parameter read tool with no output schema and no annotations, the description covers the essential: what is returned (remaining quota) and the governing limit. A minor gap is the absence of any note on quota reset cadence or siteUrl expectations.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description does not elaborate on siteUrl format (domain vs. full URL, verified-site requirement), adding no meaning beyond the schema.

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 uses a specific verb and resource: 'Get the remaining URL submission quota for a site in Bing.' It is clearly distinguishable in substance from siblings like bing_submit_url or bing_get_url_info, but it never explicitly contrasts itself with them, so it stops 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 Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is a pre-flight check before submitting URLs, since the description mentions the submission quota and daily limit. There is no explicit 'use this before X' or 'do not use this for Y' guidance pointing at bing_submit_url or bing_submit_url_batch.

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