Skip to main content
Glama

Citemark

Get my tracking results

get_my_tracking
Read-onlyIdempotent

Summarizes the websites the user tracks in their Citemark account: for each, how often AI assistants named it in the last 7 days, the competitor named most, and a link to its dashboard. Needs the user's Citemark account.

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

Input Schema

NameRequiredDescriptionDefault
websiteNoOptional: only this tracked website, like acme.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond them: a fixed 7-day window, the exact per-site contents returned, and the account requirement. It does not mention result limits or empty-account behavior, keeping it short of a 5.

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 output contents are front-loaded in the first clause, followed by a short prerequisite sentence; there is no filler. The first sentence is somewhat dense with a comma-separated list, but every element is substantive.

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?

For a one-optional-param read tool with full annotation coverage and no output schema, the description is essentially complete: it states scope, time window, return contents, and the account prerequisite. Only minor operational details (empty results, result caps) are absent.

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 coverage is 100% and the single optional "website" parameter is already documented with an example format in the schema. The description adds no further semantics about it (no notes on matching behavior or case sensitivity), so it sits at the baseline where the schema does the work.

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?

"Summarizes the websites the user tracks in their Citemark account" gives a specific verb (summarizes) and resource (tracked websites), and enumerates the three things returned per site (mention frequency, top competitor, dashboard link). It does not explicitly contrast with siblings like check_ai_visibility or get_ai_picks, but the scope is concrete enough to distinguish it in practice.

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?

"Needs the user's Citemark account" supplies a prerequisite for use, and the purpose sentence implies this is the read-side companion to start_tracking. However, there is no explicit when-to-use/when-not guidance and no named alternative for adjacent tasks (e.g. visibility checks vs. tracking summary), so the agent must infer its place in the workflow.

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