Skip to main content
Glama
Sign In
paid-media-mcp

paid-media-mcp

by kenlim5656
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_test

Retrieve complete details of an A/B test including hypothesis, variant results, confidence level, metric lift, conclusion, and action taken.

Instructions

Get full details for a single test: hypothesis, all variants, results, confidence level, primary metric lift, conclusion, and action taken.

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": {
      "test_id": "<test_id>"
    },
    "name": "get_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYesTest ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It describes the output but does not state that the operation is read-only, non-destructive, or require specific permissions. For a data retrieval tool, this is a notable gap as the agent cannot infer safety from the description alone.

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 description is a single sentence that efficiently communicates the tool's purpose and output. It lists key fields without excessive detail. While it could be structured into bullet points for clarity, the conciseness is appropriate for a straightforward retrieval tool.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema), the description adequately covers the output by listing relevant fields. It does not include edge cases or error conditions, but for a basic 'get by ID' tool, the completeness is sufficient.

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% with a single parameter 'test_id' described as 'Test ID'. The description adds meaning by enumerating the output fields (hypothesis, variants, results, etc.), helping the agent understand what constitutes 'full details' and how to interpret the response. This exceeds the baseline of 3.

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 uses a specific verb 'Get' and explicitly names the resource 'full details for a single test', listing the fields included (hypothesis, variants, results, etc.). This clearly distinguishes it from sibling tools like list_tests which returns a list, or get_test_learnings which may have a different scope.

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 implies that this tool is for retrieving comprehensive details for one test, contrasting with list_tests for listing. However, it does not explicitly state when not to use it or mention alternatives like get_test_learnings. The context signals and sibling list make the intended use clear, but exclusions are missing.

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

Deploy Server

Other Tools