Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Rename a campaign folder

argorant_rename_folder
Idempotent

Give a campaign folder a new name; its campaigns stay in it. Use it only to rename. To move campaigns between folders use argorant_move_campaign_to_folder, and to find the folder_id use argorant_list_folders. 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": {
      "folder_id": "<folder_id>",
      "name": "<name>"
    },
    "name": "argorant_rename_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name.
folder_idYesThe folder's id, from argorant_list_folders.

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 one genuinely useful behavioral fact beyond them: the folder's campaigns remain in place after the rename, which clarifies the blast radius of the mutation. It does not mention permissions, error cases, or name-collision behavior, which keeps it from a 5.

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 short sentences: the operation and its invariant first, then routing to alternatives and prerequisites. Every clause carries information; the docs link is a single trailing token and does not interrupt the actionable content.

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 idempotent rename with full schema coverage and an output schema that documents the response, the description covers operation, invariant, prerequisites, and alternatives. Nothing an agent needs in order 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 carry their own descriptions, so the baseline is 3. The description's mention of argorant_list_folders to obtain folder_id restates what the schema already says ("The folder's id, from argorant_list_folders") and adds no constraint or format detail beyond the min/maxLength already declared.

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?

"Give a campaign folder a new name" is a specific verb+resource, and "its campaigns stay in it" immediately scopes the operation as a rename rather than a move or rebuild. An agent can distinguish it from argorant_move_campaign_to_folder or argorant_create_folder without opening any 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?

"Use it only to rename" is an explicit when-not statement, and the description names two concrete alternatives with their triggering conditions: argorant_move_campaign_to_folder for moving campaigns and argorant_list_folders for obtaining the folder_id. Nothing about tool selection is 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