Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

Contact StealAds support

contact_support
Idempotent

Sends a help request, problem report or feature suggestion from the user to the StealAds team and returns a confirmation that it was saved. For when the user asks for help or reports that something is wrong; it passes the message on and does not answer it. Identical messages within a day are combined, and an account can send up to five new messages per hour.

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": {
      "kind": "<kind>",
      "message": "<message>"
    },
    "name": "contact_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYeshelp for a question; bug_report for a problem; feature_request for a suggestion.
messageYesThe message the user wants to send, in their words, with only the details support needs to help. Up to 4,000 characters.

Output Schema

NameRequiredDescriptionDefault
messageNomessage value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / message / description
      Previous value: -"The message the user wants to send to StealAds support. Include only details needed to help."New value: +"The message the user wants to send, in their words, with only the details support needs to help. Up to 4,000 characters."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare it is a non-read, open-world, non-destructive, idempotent write, but do not convey operational limits. The description adds the rate limit (five new messages per hour per account), the deduplication rule (identical messages within a day are combined), and the return behavior (confirmation that it was saved) — exactly the context an agent needs before calling a write tool that cannot be undone.

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?

Two sentences, front-loaded with the action and result, followed by the usage condition and then the behavioral constraints. Every clause — dedup, rate limit, no-answer — carries distinct decision-relevant information with no filler.

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 two-parameter write tool with an output schema and full annotation coverage, the description supplies the triggering condition, what is transmitted, what is returned, and the two operational constraints that could otherwise cause a surprising failure. Nothing an agent needs to invoke it correctly is missing.

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 both parameters are fully documented with enum values, length bounds, and content guidance, so the schema carries the parameter burden. The description only restates the three message kinds already encoded in the `kind` enum and adds no new semantics such as how to phrase `message` or how it interacts with the dedup rule.

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 a specific verb and resource (sends a help request / problem report / feature suggestion to the StealAds team), enumerates the three message kinds that match the `kind` enum, and explicitly delimits scope with 'it passes the message on and does not answer it.' No sibling in the supplied list performs support submission, so there is nothing to confuse it with.

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

Usage Guidelines4/5

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

'For when the user asks for help or reports that something is wrong' gives a clear triggering condition for the agent. It stops short of naming alternatives or explicit when-not conditions, though 'does not answer it' usefully rules out expecting a resolution from this call.

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

All StealAds toolsInspect
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