BlogSEO

Convert credits to backlink credits

convert_credits_to_backlink_credits

Destructive

Converts AI brain credits into backlink credits at a fixed rate of 1 AI brain credit = 5 backlink credits, so the exchange network can place more backlinks to the website. The conversion is irreversible: backlink credits can never be turned back into AI brain credits. Cost rule: the amount passed is the number of AI brain credits spent (1 to 100 per call). Returns the new balances. Costs AI brain credits (see the cost rule above), charged before the work, not refunded on failure. Requires an active subscription or free trial. Pass confirm=true to acknowledge the AI brain credits charge; without it the tool only returns the cost and your balance. Pass website_id when the account has several websites (see get_account).

Input Schema

TableJSON Schema

Name	Required	Description
`amount`	Yes	Number of AI brain credits to convert (each one becomes 5 backlink credits).
`confirm`	No	Set to true to acknowledge the AI brain credit charge. Omit it to only get the cost and your balance.
`website_id`	No	Website id from get_account. Optional when the account has a single website.

Output Schema

TableJSON Schema

Name	Required	Description
`credits_balance`	No	Current AI brain credits balance; only with requires_confirmation.
`credits_required`	No	AI brain credits the call would charge; only with requires_confirmation.
`ai_credits_balance`	No
`ai_credits_converted`	No
`credits_balance_after`	No	AI brain credits balance after this call.
`requires_confirmation`	No	Present when the tool did not run: it needs confirm=true. The other fields are then absent.
`backlink_credits_added`	No
`backlink_credits_balance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A5/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing that the conversion is irreversible, that credits are charged before the work, and that charges are not refunded on failure. These are important behavioral facts not derivable from destructiveHint alone.

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?

The description is dense but every sentence earns its place, covering rate, irreversibility, cost rule, subscription requirement, confirmation behavior, and website_id handling. It is front-loaded with the core conversion fact and then layers necessary operational details.

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?

The description covers all essential operational dimensions: cost, irreversibility, failure refunds, authentication requirements, confirmation flow, and parameter conditions. With an output schema present, the return value details are adequately handled elsewhere.

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

Parameters5/5

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

Although the schema already covers all parameters, the description adds meaning: amount is defined as AI brain credits spent with a 1-to-100 range, confirm is tied to acknowledging the charge, and website_id is tied to multi-website accounts and the get_account source. This is strong value beyond the schema.

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?

The description names the exact verb and resource: it converts AI brain credits into backlink credits. It also specifies the fixed conversion rate and the intended purpose, which clearly distinguishes it from any sibling tool.

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?

The description provides explicit when-to-use and how-to-use guidance: it states the subscription/free-trial requirement, explains the confirm=true prerequisite for actually performing the conversion, and gives the website_id condition for multi-website accounts. This leaves little to inference.

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

All BlogSEO 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.