IDDET

mcp_create_ad_campaign

Sponsorise une actfile en créant une campagne publicitaire LOCALE (aucun service externe requis pour l'instant). La campagne est activée immédiatement ; le budget n'est pas obligatoire tant qu'aucun moyen de paiement n'est branché — il est juste enregistré à titre informatif.

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": {
      "auth_token": "<auth_token>",
      "actfile_id": "<actfile_id>"
    },
    "name": "mcp_create_ad_campaign"
  }
}

Input Schema

Name	Required	Default
`daily`	No
`currency`	No	USD
`actfile_id`	Yes
`auth_token`	Yes
`budget_amount`	No
`target_country`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

addedInput schema / properties / budget_amount / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / budget_amount / default
```
Added value: +null
```
removedInput schema / properties / budget_amount / type
```
Removed value: -"number"
```

changedInput schema / required

Previous value: -[
-  "auth_token",
-  "actfile_id",
-  "budget_amount"
-]New value: +[
+  "auth_token",
+  "actfile_id"
+]

AddedSep 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the campaign is activated immediately, the budget is optional and only recorded for informational purposes, and that no external service is required. This is meaningful behavioral transparency beyond a simple 'create' statement, covering key side effects and constraints. It does not mention failure modes or error behaviors, but the disclosed information is valuable.

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 two sentences, clearly structured, with the main purpose front-loaded. Every sentence adds value, and there is no redundancy. It is concise yet informative.

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 that there are 6 parameters with zero schema descriptions, no output schema, and no annotations, the description is incomplete. It does not explain parameter semantics, expected inputs, or what the tool returns. It also lacks error handling or preconditions. An agent would need additional information to call this tool correctly, especially for parameters like daily, currency, and target_country.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all parameters. It only indirectly addresses the budget parameter (optional, informational) and mentions the local aspect. It does not explain the meaning of daily, currency, target_country, or the required auth_token and actfile_id. This is insufficient for an agent to correctly construct the parameters without additional information.

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 clearly states the tool's function: sponsoring an actfile by creating a local advertising campaign. It specifies that no external service is required and that the campaign is activated immediately, distinguishing it from potential external ad services. It is specific, not a tautology, and uses a clear verb-resource structure.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: to sponsor an actfile immediately. It mentions that the budget is optional and no payment is needed, which informs the user of the current operational context. However, it does not explicitly name alternative tools or provide when-not-to-use guidance. The context is clear enough for a straightforward create operation.

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

All IDDET tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?