Skip to main content
Glama

ScrapingBee usage

get_scrapingbee_usage
Read-only

Read real-time credit and concurrency usage for the authenticated ScrapingBee account.

Note: This endpoint is rate-limited to 6 calls per minute and does not count against the account's concurrency limit.

Returns: max_api_credit, used_api_credit, max_concurrency, current_concurrency, renewal_subscription_date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_scrapingbee_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds genuinely useful context beyond them: a 6-calls-per-minute rate limit and the fact that calls don't count against the account's concurrency limit. It does not say what error surfaces when the rate limit is exceeded, which keeps it short of a 5.

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?

Front-loaded with the purpose in the first sentence, followed by the rate-limit caveat and a compact field list. The 'Returns:' block partly duplicates the existing output schema, so it is slightly redundant but short enough not to be wasteful.

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 no-parameter read-only tool with an output schema and readOnlyHint, the description covers what is needed: what is read, the rate limit, and the concurrency exemption. Minor gaps remain around auth requirements and rate-limit-exceeded behavior, but the core calling information is present.

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

Parameters4/5

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

The tool takes zero parameters, so per the baseline there is no parameter semantics burden and the description is not expected to compensate. Nothing here misdescribes the empty input object.

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?

States a specific verb and resource — 'Read real-time credit and concurrency usage for the authenticated ScrapingBee account' — which is unambiguous and clearly distinct from every sibling, all of which are scraping/data-extraction endpoints. An agent can identify this as the account-quota tool without opening the schema.

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 only implied: an agent infers it should call this to check remaining credits or concurrency before or after scraping jobs. There is no explicit when-to-use statement, no exclusion, and no mention of any alternative for account-level information.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources