ScrapeCreators MCP Server

Get daily usage

scrapecreators_get_daily_usage

Read-onlyIdempotent

Retrieve aggregated daily usage stats for a named private account over the last 30 days, showing total credits consumed and requests per day to track consumption.

Instructions

Returns aggregated daily usage statistics for the last 30 days, including total credits consumed and number of requests per day. 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_daily_usage"
  }
}

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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful fixed 30-day window and the exact metrics returned, but says nothing about pagination, result size, rate limits, or auth requirements.

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 core purpose and confined to two short sentences with no filler. The final fragment "Account metadata read." is slightly cryptic but functionally a categorization tag.

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-argument read-only aggregate tool, stating the window and the returned metrics covers what an agent needs; no output schema exists but the return contents are summarized. Missing only retrieval-edge behavior such as pagination or empty-window handling.

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?

Only one optional parameter and schema coverage is 100%, so the schema already carries the semantics, including the important note that "account" selects local credentials rather than a remote ID. The description adds no parameter meaning, which is acceptable at this coverage.

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?

States a specific verb ("Returns") and resource ("aggregated daily usage statistics") with concrete scope: last 30 days, credits consumed, requests per day. The detail implicitly separates it from scrapecreators_get_credit_balance and scrapecreators_get_request_history, though no sibling is named explicitly.

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?

There is no when-to-use, when-not-to-use, or alternative-routing guidance. The trailing tag "Account metadata read." is a category label, not usage direction, and the many account/tiktok/instagram siblings are left unaddressed.

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

Deploy Server