Skip to main content
Glama

askr_hide_products

Hides specified products from the Askr store by their d IDs, skipping any IDs not listed and returning the hidden IDs. Use dry_run to preview changes without publishing.

Instructions

Hide products from the Askr store this agent's catalog key writes, by their d ids. An id that is not listed is skipped. Returns the ids hidden.

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": {
      "ids": "<ids>"
    },
    "name": "askr_hide_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesThe `d` ids of products to hide from the store.
dry_runNoReport what would change, publish nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.61

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses the effect (hiding), the partial-batch semantics, and the return value ('Returns the ids hidden'), which is genuine behavioral value. It does not say whether hiding is reversible, what permissions the catalog key needs, or how it interacts with the 200-id cap the schema imposes.

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 short sentences, effect first, exception second, return value last — nothing wasted and no redundancy with 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 two-parameter mutation tool with a fully documented schema and no output schema, this covers effect, partial-failure behavior, and return value adequately. The remaining gap is the mutation's reversibility and permission profile, which matters more here because no annotations exist to cover it.

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%, so both `ids` and `dry_run` are already documented in the schema; baseline 3 applies. The description adds only marginal meaning beyond that — it reinforces that ids are `d` ids and that unlisted ids are no-ops, but says nothing about `dry_run` beyond what the schema states.

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?

Names a specific verb and resource ('Hide products from the Askr store') and scopes it to 'this agent's catalog key writes,' which implicitly separates it from the upsert sibling. An agent can tell what it does, though there is no explicit contrast with askr_upsert_products or askr_preview_diff.

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 implied by the verb (remove products from the store) and the description clarifies partial-batch behavior ('An id that is not listed is skipped'). It never states when to prefer this over askr_upsert_products or when to pre-check with askr_preview_diff, so the agent must infer routing.

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