Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Move a campaign into a folder

argorant_move_campaign_to_folder
Idempotent

Put a campaign into a folder, move it to another folder, or take it out of its folder by leaving folder_id out. Use it to organise campaigns; for labels that cross folders use argorant_tag_campaigns. Only the grouping changes; the campaign, its people and its sending stay as they are. More in the docs at https://docs.argorant.com/docs/agents/tools#campaigns

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "argorant_move_campaign_to_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idNoThe folder from argorant_list_folders. Leave it out to take the campaign out of its folder.
campaign_idYesThe campaign's id, from argorant_list_campaigns.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds real value by scoping the side effect — 'only the grouping changes; the campaign, its people and its sending stay as they are' — which reassures an agent that no campaign content or sending state is touched. It does not discuss permissions or failure modes, but that is a minor gap given the annotation coverage.

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 tight sentences: capability first, sibling disambiguation second, side-effect reassurance third, plus a docs pointer. Every sentence carries distinct information and nothing is repeated redundantly.

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?

A simple two-parameter grouping tool with an output schema, full schema coverage and a clear non-destructive guarantee. An agent has everything needed to call it correctly and to predict its effect.

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 coverage is 100% and both property descriptions already state where the ids come from and that omitting folder_id removes the campaign from its folder. The description restates the omission semantics but adds no new syntax or format detail beyond the schema, so the baseline 3 applies.

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?

Uses a concrete verb and resource and enumerates all three modes of operation: put into a folder, move between folders, and remove from a folder. It explicitly routes label-based grouping to argorant_tag_campaigns, so an agent can distinguish it from that sibling without opening either schema.

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?

States the when-to-use case (organising campaigns), names the alternative tool and the condition that selects it (labels that cross folders → argorant_tag_campaigns), and explains the removal case up front. Nothing left to inference.

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

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