Skip to main content
Glama

Browse public rankings

aimrank_discover_public_rankings
Read-onlyIdempotent

Browse public rankings — agent equivalent of surfing aimrank.io.

Filters: category, media_type ("text" | "image" | "audio" | "video"), sort ("trending" | "recent" | "most_votes" | "random"), limit 1-50. Each result embeds share assets so the agent can hand any ranking back to the user as a clickable link without a follow-up call.

api_key is optional on the public endpoint; on /mcp/mcp a missing key is refused.

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": "aimrank_discover_public_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNotrending
limitNo
api_keyNo
categoryNo
media_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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 readOnly/openWorld/idempotent, and the description adds genuinely non-derivable behavior: results embed share assets (avoiding a second call) and api_key is optional on the public endpoint but required on /mcp/mcp. It stops short of rate limits, pagination, or error behavior, so not 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?

Front-loaded verb phrase, then a compact filter block, then the share-asset benefit and auth caveat. The 'surfing aimrank.io' framing is flavor rather than information, but it is a single clause and nothing else is padded.

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?

With an output schema present, return values need not be spelled out, and the description still flags the embedded share assets plus the api_key caveat. What remains uncovered is minor: what values 'category' accepts and whether results are paginated beyond limit.

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

Parameters5/5

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

Schema description coverage is 0% and the schema carries no enums, yet the description supplies the accepted values for sort ('trending' | 'recent' | 'most_votes' | 'random'), the media_type set ('text' | 'image' | 'audio' | 'video'), and the limit bound (1-50). It also explains api_key's optionality, compensating fully for the bare schema.

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?

States a specific verb and resource ('Browse public rankings') and frames the scope as public/unauthenticated browsing. It does not name a sibling such as aimrank_get_ranking or aimrank_search_entities to delimit the alternative path, so it is clear but not sibling-differentiated.

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 context is implied by 'agent equivalent of surfing aimrank.io' and by the note that results embed share assets so the agent can hand a clickable link back to the user without a follow-up call. There is no explicit when-not guidance or named alternative for retrieving a single ranking versus browsing.

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