Skip to main content
Glama

Outil.io

Get campaign report

get_campaign_report
Read-only

Bilan d’une campagne commerciale en un appel, pour searchId (recherche de prospects), journeyId (parcours de vente) ou tag (étiquette de campagne ou tag des contacts) : prospects trouvés, contactés par canal, premiers messages et relances, e-mails ouverts/cliqués/en rebond, réponses par intention et taux de réponse, appels et rendez-vous (log_activity), opportunités, devis envoyés/acceptés et CA encaissé (centimes TTC). Un bloc indisponible est signalé sans bloquer le reste.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_campaign_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
sinceNo
searchIdNo
journeyIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: an unavailable block is reported without failing the whole response (partial-failure semantics), revenue is expressed in centimes TTC, and appointments come from log_activity. It still does not state whether selectors can be combined or what happens when none is supplied.

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?

The core purpose is front-loaded in the opening clause, and given there is no output schema the long metric enumeration largely earns its place as a return-value preview. The middle section is a single run-on list that would read faster broken up, which keeps it from a 5. No filler sentences.

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

Completeness3/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 compensates well by enumerating the report contents and stating the partial-failure rule. Against a 4-parameter tool with 0% schema coverage, though, the unexplained `since` parameter and the unstated combination rules for searchId/journeyId/tag leave real gaps for an agent deciding how to call it.

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 0%, so the description must carry the load. It usefully glosses three of four parameters (searchId = recherche de prospects, journeyId = parcours de vente, tag = étiquette de campagne ou tag des contacts). However `since` gets no explanation of format or meaning, and mutual exclusivity among the three selectors is never stated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Bilan d'une campagne commerciale') and enumerates the exact metrics returned (prospects trouvés, contactés par canal, e-mails ouverts/cliqués/en rebond, réponses par intention, appels et rendez-vous, devis, CA encaissé). It also clarifies the three targeting modes (searchId, journeyId, tag), which lets an agent distinguish it from generic report siblings. It stops short of naming a sibling it is not, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is implied by the selector descriptions — the agent learns it must choose a prospect search, a sales journey, or a campaign/contact tag — but there is no explicit statement of when to prefer this over report_collection, report_reply, or get_newsletter_stats. The `since` parameter is never mentioned, so temporal-scoping guidance is absent. Adequate but leaves routing decisions to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.