Blog2Social - Social Media Publishing

Retrieve account usage overview

account.overview

Read-onlyIdempotent

Use this tool when the user asks for an account-level overview of Blog2Social API credit usage.

It returns the current credit balance and aggregated usage totals grouped by day, endpoint, and social network.

The optional days parameter must be an integer between 1 and 30. If omitted, the endpoint default applies.

The results describe aggregated account usage. They do not provide performance metrics or analytics for individual published social media posts. Use posts.insights for individual post performance.

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": "account.overview"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Number of calendar days to include, from 1 to 30.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 9, 2026

removedOutput schema / properties / data / properties / balance

Removed value: -{
-  "description": "Current available credit balance.",
-  "type": "number"
-}

addedOutput schema / properties / data / properties / credit_open_balance

Added value: +{
+  "description": "Current available credit balance.",
+  "type": "number"
+}

changedOutput schema / properties / data / required

Previous value: -[
-  "credit_usage_total",
-  "balance",
-  "days"
-]New value: +[
+  "credit_usage_total",
+  "credit_open_balance",
+  "days"
+]

AddedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world status, so the bar is lower. The description still adds real context: the response is aggregated by three dimensions, the day window is capped at 30, and the tool deliberately excludes per-post analytics. It does not mention pagination or refresh/caching behavior, which is the remaining gap for an openWorld hint tool.

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 trigger condition, then the return shape, then the constraint, then the exclusion — a sensible order. Minor redundancy in saying the data is 'aggregated account usage' twice (in the return sentence and the exclusion sentence), but nothing extraneous enough to trim materially.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations, a fully documented single parameter, and an output schema already present, the description needs only to establish trigger, scope, and exclusions — all of which it does. An agent has everything required to call this correctly and to route away from it when appropriate.

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 description coverage is 100% and the single parameter already documents 'Number of calendar days to include, from 1 to 30' with min/max constraints. The description restates the same 1-30 bound and adds only that an endpoint default applies when omitted — a marginal addition, so 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?

States a specific verb and resource: returns the current credit balance plus aggregated usage totals broken down by day, endpoint, and social network. That level of detail lets an agent distinguish it from credits.balance (balance only) and posts.insights (per-post performance) without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Opens with an explicit trigger ('when the user asks for an account-level overview of Blog2Social API credit usage') and closes with an explicit exclusion plus a named alternative ('do not provide performance metrics... Use posts.insights'). The only unaddressed overlap is with credits.balance, which returns the same balance figure, but the primary routing decision is unambiguous.

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

All Blog2Social - Social Media Publishing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?