Skip to main content
Glama
Sign In

Fledly

by app.fledly
OverviewDiscussionsAdmin

Stop tracking an App Store search

untrack_keyword
DestructiveIdempotent

Stops tracking one search for one of the user's apps. Rank history already collected stays in Fledly, but the search no longer counts toward the plan limit and is no longer measured.

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": {
      "app_id": "<app_id>",
      "term": "<term>"
    },
    "name": "untrack_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe tracked search.
app_idYesApp Store id of a tracked app.
countryNoApp Store country, two-letter code such as us, gb or fi.us

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 flag destructiveHint=true and idempotentHint=true, so the description's real contribution is clarifying what 'destructive' means here: rank history is retained in Fledly, the search stops counting toward the plan limit, and measurement ends. That is substantive context beyond the annotations, though it omits what error behavior looks like when the term is not currently tracked.

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?

Two tight sentences with the core action front-loaded followed by the consequences. No filler, no restatement of the title.

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 simple three-parameter mutation with no output schema and full annotation coverage, the description supplies the outcome and data-retention semantics an agent needs to act confidently. Only the not-currently-tracked case is left unaddressed.

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%, so term, app_id and country are already documented in the schema. The description reinforces the singular scope ('one search for one of the user's apps') but adds no detail about country, defaults, or accepted id formats, 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?

The description names a specific verb and resource ('Stops tracking one search') and scopes it to 'one of the user's apps', which makes it immediately distinguishable from the sibling track_keywords/track_app tools. An agent can identify the operation 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is the inverse of track_keywords and that it applies to an already-tracked search, but the description never states prerequisites (must the term already be tracked?) or points to the re-tracking alternative. No explicit when-not guidance.

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

All Fledly toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources