Galatic.ai

Marketing analytics

get_marketing_analytics

Read-onlyIdempotent

Read analytics for one marketing campaign. report "performance" returns { items: [{ itemId, score, metrics }], totalItems }, best score first; "geo" returns performance by location and time slot; "titles" returns title-pattern A/B results; "history" returns { history } of publish records (platform, status, externalPostUrl, title, timeSlot). campaignId is required by every report (400 without it, 403 if it is not the caller's); get it from auto_publish_list_posts. Read-only.

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": {
      "report": "<report>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_marketing_analytics"
  }
}

Input Schema

Name	Required	Description
`report`	Yes
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`campaignId`	No	Required by the server for every report. From auto_publish_list_posts.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026
- addedInput schema / properties / campaignId / description
```
Added value: +"Required by the server for every report. From auto_publish_list_posts."
```
First observedOct 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, but the description adds real behavioral context beyond them: sort order ('best score first'), ownership-based 403 authorization, 400 on missing campaignId, and the return shape per report. The 'Read-only' statement is consistent with, not contradictory to, annotations.

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?

Front-loads the purpose, then packs report semantics, prerequisite, and error behavior into a few dense clauses with no filler. Every sentence carries information an agent needs before calling.

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?

No output schema exists, and the description compensates by naming the returned fields for performance and history and describing the shape of the geo and titles results. Combined with the prerequisite chain for campaignId, nothing needed to call 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 80% and the enum values are documented in the schema, yet the description adds per-enum semantics (what 'geo', 'titles', and 'history' actually return) that the schema cannot express. It also reinforces campaignId's origin. The analytics-only params (context, llm_model) are left to the schema, which already explains them well.

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?

Opens with a specific verb and resource ('Read analytics for one marketing campaign') and then enumerates the four report modes with what each one returns, which is far more precise than the title 'Marketing analytics'. An agent can immediately distinguish this from siblings like auto_publish_list_posts or get_job_status.

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?

Gives explicit prerequisites: campaignId required by every report, sourced from auto_publish_list_posts, with 400/403 consequences for the wrong or missing value. It does not explicitly state when to prefer other sibling tools over this one, so it falls just short of a 5.

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

All Galatic.ai 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.