Skip to main content
Glama

Appeak Pro: App Store Optimization

Search the ASO Guide

search_aso_guide
Read-onlyIdempotent

Finds articles in Appeak Pro's ASO Guide for an App Store Optimization question (keywords, screenshots, ratings, localization, Google Play tags, AI discoverability...).

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": {
      "query": "<query>"
    },
    "name": "search_aso_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe question, e.g. "how to pick google play tags"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the helpful framing that results are guide articles (informational retrieval, not live data), but it says nothing about result count, relevance ranking, or empty-result behavior.

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?

One sentence, front-loaded with the verb and resource, and the topic list is a compact and useful scoping aid. The embedded parenthetical plus ellipsis is slightly loose but not wasteful.

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?

A single-parameter, read-only retrieval tool with 100% schema coverage and no output schema; the description establishes what is searched, what kind of input is expected, and the safety profile is carried by annotations. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already gives an example for query, so baseline is 3; the description goes slightly beyond by enumerating the topic space the query should cover (keywords, screenshots, ratings, localization, Google Play tags, AI discoverability) and framing it as a question. No syntax or length guidance is added.

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?

Specific verb (Finds) plus resource (articles in Appeak Pro's ASO Guide) and it names the topical domains covered, which distinguishes it from sibling tools like check_keyword_ranks or audit_listing. It doesn't explicitly name a sibling as the alternative, so a 4 rather than 5.

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?

The parenthetical topic list implies when the tool is useful (conceptual ASO questions), but there is no explicit when-to-use versus when-not guidance and no named alternative for adjacent tasks such as auditing a listing or checking ranks. Usage is inferable but left to the agent.

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