Widely

Create a campaign invite code

create_campaign_code

Creates a vanity invite code, such as ADS50, that counts signups from one placement. It pays no reward and charges nothing. Omitted confirm returns a preview on every client.

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": {
      "code": "<code>",
      "name": "<name>"
    },
    "name": "create_campaign_code"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	3 to 24 letters and numbers.
`name`	Yes
`confirm`	No	Omitted returns a preview on every client. True creates the code.
`creative_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses useful behavioral facts: no reward is paid, nothing is charged, and omitting confirm returns a preview. That preview note is genuinely additive because the standard client tool schema barely covers it. It does not say what happens when the code already exists, which matters for a non-idempotent create.

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?

Three short sentences, front-loaded with purpose, then cost behavior, then the preview caveat. No wasted words and no restatement of the title.

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

Completeness3/5

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

For a 4-parameter mutation tool with no output schema, the description covers cost and the preview path but leaves gaps: preview return shape, behavior on duplicate codes, and the role of creative_id. An agent could call it, but would be guessing on parameter meaning and failure modes.

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

Parameters2/5

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

Schema coverage is 50%: code and confirm are documented in the schema, while name and creative_id are bare. The description adds a format example for code but says nothing about what name or creative_id mean or how creative_id ties the code to a placement/creative. It does not compensate for the undocumented half of the parameters.

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?

Opens with a specific verb+resource ("Creates a vanity invite code") and adds a concrete example ("ADS50") plus scope ("counts signups from one placement"). It does not name the near siblings update_campaign_code or list_campaign_codes, so the agent must infer create-vs-update-vs-list on its own.

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

Usage Guidelines3/5

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

There is no explicit when-to-use/when-not-to-use statement or named alternative, but the preview-on-omitted-confirm note implies the intended two-step workflow (preview, then confirm). Guidance is inferable rather than stated.

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

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