Skip to main content
Glama

Get my Kliqo briefing

get_briefing
Read-onlyIdempotent

Everything that needs attention in the member's Kliqo workspace, checked in one call: visibility change this week and this month, who moved ahead, prompts AI answers without naming them, sites where competitors get cited instead, the most valuable open actions, results of finished actions, AI crawler errors and whether answers are still coming in, with suggested next steps. Use when the member asks how their brand is doing in AI answers, what changed, or what to work on. 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_briefing"
  }
}

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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description usefully adds that sign-in to Kliqo is required and that the call is read-only. It adds no detail on response size, latency, or whether the aggregate is expensive, which would matter for a broad fan-out call, but with an output schema present that gap is minor.

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 "everything in one call" framing is front-loaded before the enumeration, and the usage sentence plus auth note follow in a logical order. The middle enumeration is a long run-on list, but each item maps to a distinct briefing section, so little could be cut without losing scope information.

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 the description needn't explain return values, and it covers purpose, trigger conditions, and the sign-in requirement. The only optional parameter is fully specified in the schema, so an agent has everything needed to call this correctly.

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 100% and the single optional `project` parameter is fully documented in the schema, so the baseline is 3. The description never mentions project scoping at all — the only reference is "the member's Kliqo workspace" — so it adds nothing beyond the schema here.

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 gives a specific verb and resource — an aggregate status check of a member's Kliqo workspace in a single call — and enumerates the concrete sections it returns (visibility change, competitor citations, open actions, crawler errors). This implicitly distinguishes it from the single-purpose siblings like get_ai_visibility or get_actions, though it never names them explicitly.

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?

"Use when the member asks how their brand is doing in AI answers, what changed, or what to work on" gives a clear triggering context for the tool. It does not state when to prefer a drill-down sibling over this overview call, so it stops short of 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