Skip to main content
Glama
Sign In

AutomateSocials

by net.automatesocials
OverviewDiscussionsAdmin

Change a campaign plan

edit_campaign_plan

Adds posts to a campaign plan, removes planned ones, or rewrites their theme and angle. This is how you add "one more post about X" without planning the campaign again. Posts already written keep their words - use edit_post for those - and removing one that is already written is refused.

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": {
      "id": "<id>"
    },
    "name": "edit_campaign_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe campaign, by id or by name.
addNoPosts to add to the plan.
removeNoDay numbers to drop, as get_campaign shows them.
updateNoChanges to planned posts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this as non-readonly, open-world, non-idempotent, and not destructive. The description adds important behavioral constraints beyond annotations: written posts keep their words, and removal of a written post is refused. It does not explain multi-operation conflict handling or atomicity, so it is strong but not exhaustive.

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 three sentences, front-loaded with the core operations and immediately followed by the key usage distinction and refusal rule. Every sentence adds useful information.

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

Completeness4/5

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

With no output schema, the description need not explain return values, and annotations already carry the safety profile. It covers the main operations, the edit_post alternative, and the written-post guardrail, though it leaves some complexity around multi-operation behavior unstated.

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%, so the nested add/remove/update fields are already well documented in the schema. The description maps the operations at a high level but does not add parameter syntax or format details beyond what the schema provides, so the baseline 3 is appropriate.

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 states specific verbs and resource: adds posts, removes planned posts, and rewrites theme/angle in a campaign plan. It clearly distinguishes the tool from edit_post by saying written posts keep their words and should be edited there instead.

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 explicit when-to-use guidance: adding "one more post about X" without replanning the campaign. It also names the alternative, edit_post, for already-written posts and states that removing a written post is refused.

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

All AutomateSocials 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