ScrapeCreators MCP Server

Get credit balance

scrapecreators_get_credit_balance

Read-onlyIdempotent

Check remaining Scrape Creators API credits for a named private account and return the current creditCount balance before making paid calls.

Instructions

Returns the number of API credits remaining on your Scrape Creators account. The response contains a single creditCount field with your current balance. Account metadata read.

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": "scrapecreators_get_credit_balance"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No	Named private ScrapeCreators account; selects credentials, not a remote account ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds that the response contains a single creditCount field, which is useful return-value context, but it omits auth/rate-limit or account-selection behavior. This is adequate but not rich.

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?

Two sentences front-load the purpose and return detail efficiently. The trailing 'Account metadata read' is mildly redundant but does not bloat the description.

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 read tool with rich annotations and full schema coverage, the description is nearly sufficient: it states what is returned via the creditCount field. It does not fully explain the optional account parameter or output format, but no output schema exists and the missing details are minor for invocation.

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 one optional parameter with 100% schema description coverage, so the schema already documents that 'account' selects credentials rather than a remote account ID. The description adds no additional parameter meaning beyond the schema; baseline 3 is appropriate.

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?

Specific verb 'Returns' and resource 'API credits remaining' with clear scope. It does not explicitly distinguish from sibling account tools like get_daily_usage or get_request_history, but the resource is unambiguous.

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 when-to-use, prerequisites, or alternatives are provided. The phrase 'Account metadata read' is a tagline rather than guidance; an agent must infer that this is for checking balance.

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

Deploy Server