Promptify

Render ad (spends credits, requires confirmation)

render_ad

First call with adId to get the real credit quote without spending. Show the user the cost and ask for approval. Only then call again with confirm: true and expectedCredits equal to totalCredits from the quote. A changed quote requires approval again. Uses the studio's paid render service; check progress and finish/export in the results URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adId": "<adId>"
    },
    "name": "render_ad"
  }
}

Input Schema

Name	Required	Description
`adId`	Yes	The ad's id, from list_ads or generate_ad_script.
`confirm`	No	True only after the user approves the quoted credit cost.
`expectedCredits`	No	The exact totalCredits the user approved.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes much further by disclosing that the call spends credits, that no credits are spent on the quote call, that user approval is mandatory, and that expectedCredits acts as a stale-quote guard. This is exactly the value-add expected of a mutation tool with minimal annotations.

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 workflow-critical instruction is front-loaded and each of the four sentences adds a distinct rule: quote first, get approval, confirm with matched credits, re-approve on quote change. No redundant wording or restatement of the title.

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?

For a credit-spending tool with no output schema, the description covers the preconditions, the cost-safety protocol, and where the output goes ('check progress and finish/export in the results URL'). An agent has everything needed to invoke it safely and know what happens afterward.

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?

Schema coverage is 100%, so per-parameter meanings are already documented. The description still adds protocol context beyond the schema: confirm and expectedCredits are only supplied on the second call, and expectedCredits must come from the returned totalCredits of the quote, which explains the relationship between the parameters rather than just their definitions.

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 uses a specific verb and resource ('render', 'ad') and immediately names the defining traits: a paid operation with a two-step quote-then-confirm flow. No sibling tool (draft, generate, get, list, stats) performs rendering, so the scope 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 Guidelines5/5

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

It gives an explicit call sequence: first call with adId only to obtain a quote, show the user the cost and request approval, then call again with confirm and matching expectedCredits. It also states the exclusion/exception case ('A changed quote requires approval again'), leaving nothing to inference.

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

All Promptify 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?