Argorant

Create a campaign folder

argorant_create_folder

Create a folder to group campaigns. Use it when the user wants a new group; to label campaigns across folders use argorant_tag_campaigns instead. Names are unique, ignoring capitals. Put campaigns into it with argorant_move_campaign_to_folder. Nothing else changes. Returns the new folder_id. 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": {
      "name": "<name>"
    },
    "name": "argorant_create_folder"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The folder's name, unique in the workspace.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, closed-world write. The description adds real behavioral context beyond that: the uniqueness constraint is case-insensitive, no other state changes ("Nothing else changes"), and the returned identifier is folder_id. It stops short of naming permission or error behavior on duplicate names, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then alternative, then constraint, then follow-up, then return value — a sensible ordering with no filler. The style is telegraphic ("Nothing else changes.") and the trailing docs link adds length, but every sentence carries information.

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 one-parameter create tool with an output schema, the description covers purpose, alternative, uniqueness semantics, side-effect scope, and the returned field. Nothing an agent needs 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.

Parameters4/5

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

Schema coverage is 100% and there is only one parameter, so the baseline would be 3. The description earns above baseline by clarifying that name uniqueness ignores capitalization, which the schema's "unique in the workspace" wording does not say.

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?

States a specific verb and resource ("Create a folder to group campaigns") and immediately distinguishes the concept from the sibling that sounds similar (argorant_tag_campaigns). An agent can pick this tool 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?

Gives an explicit when-to-use condition ("when the user wants a new group") plus an explicit alternative and the condition that selects it ("to label campaigns across folders use argorant_tag_campaigns instead"). It also names the natural follow-up tool (argorant_move_campaign_to_folder), covering the whole workflow.

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

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