Joy Trust Network

create_campaign

Create a marketing campaign

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": {
      "agent_id": "<agent_id>",
      "name": "<name>",
      "campaign_type": "<campaign_type>",
      "platform": "<platform>"
    },
    "name": "create_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Campaign name
`content`	No	Campaign content
`agent_id`	Yes	Agent ID creating the campaign
`platform`	Yes	Target platform
`scheduled_at`	No	ISO timestamp to schedule (optional)
`campaign_type`	Yes	Type of campaign

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden, but it only restates the action. It doesn't disclose side effects, e.g., whether the campaign is published immediately, requires permissions, or how scheduling works.

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 a single sentence with no redundant words, making it extremely concise. It is appropriately sized in terms of length, though it lacks substantive detail.

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

Completeness2/5

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

Given a relatively complex tool with 6 parameters, enums, and no output schema or annotations, the one-sentence description is inadequate. It doesn't explain the campaign creation workflow, required fields, or expected behavior.

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?

All 6 parameters have descriptions in the schema (100% coverage), so the schema already documents them. The tool description adds no additional parameter meaning, so baseline 3 is appropriate.

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?

The description uses a specific verb 'create' and resource 'marketing campaign', clearly indicating the action. It distinguishes from sibling tools like list_campaigns by the verb, but adds little nuance beyond the tool name.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, no exclusions, and no context about scheduling or platform selection.

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

All Joy Trust Network 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?