Skip to main content
Glama

Get the impact of finished actions

get_impact
Read-onlyIdempotent

For actions marked done: how often AI named the member's brand (and used their site as a source) in the 14 days before vs the 14 days after, on the same prompts and models. Shows "Measuring" until the after-window has enough answers. Use for "did our changes work?". Needs sign-in to Kliqo (read-only).

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_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoProject name, domain or id; leave out for the workspace's current project

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the already-declared readOnly/idempotent/non-destructive profile, it adds the auth requirement (sign-in to Kliqo, read-only) and a real runtime behavior: results show 'Measuring' until the after-window has enough answers. That pending-state disclosure is exactly the kind of thing an agent needs to interpret an empty or partial result, though it does not quantify the wait.

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?

Three sentences, each doing distinct work: the metric definition first, the pending-state caveat second, the use case and auth last. No filler, and the core definition is front-loaded.

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?

With an output schema present, return-shape detail is unnecessary; annotations already cover the safety profile and a single optional param is fully described in schema. The remaining description gaps an agent would care about (measurement window, transitional state, auth) are all covered.

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?

Only one optional parameter and schema description coverage is 100%, so the schema already fully documents 'project' including the fallback to the workspace's current project. The description adds nothing about the parameter, so the baseline 3 applies.

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?

It names a concrete measurement (brand mentions and site citations by AI), a concrete comparison design (14 days before vs 14 days after, same prompts and models), and a concrete population (actions marked done). That design is functionally distinct from siblings like get_ai_visibility or get_prompt_performance, so an agent can route to it without opening the schema.

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?

It states the decision it answers ('did our changes work?'), which gives a clear trigger for selection. It stops short of naming exclusions or an alternative tool for adjacent questions (e.g. current visibility), so it is strong context but not full when/when-not guidance.

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.

Resources