rank_categoriesRetrieve rank tab category configurations for the popularity leaderboard, then use the second_tags key to filter rank lists.
Get rank tab category configurations for the popularity leaderboard. Pass a second_tags key (e.g. hot_all-us) to rank_list.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| first_tags | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.6.0Output schema / $defs / RankFirstTag / properties / key / descriptionRemoved value: -"Category key."Output schema / $defs / RankFirstTag / properties / name / descriptionRemoved value: -"Display name."Output schema / $defs / RankFirstTag / properties / second_tags / descriptionRemoved value: -"Sub-categories. Pass a `second_tags[].key` to `rank_list`."Output schema / $defs / RankSecondTag / properties / key / descriptionRemoved value: -"Tab key to pass to `rank_list` (e.g. \"hot_all-us\")."Output schema / $defs / RankSecondTag / properties / market / descriptionRemoved value: -"Market this tab covers, e.g. \"US\" / \"HK\"."Output schema / $defs / RankSecondTag / properties / name / descriptionRemoved value: -"Display name."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved value: -"Returned by `rank_categories`. Wraps a `first_tags` array of rank tab\ncategory configurations for the popularity leaderboard. Subset of the wire\nresponse."Output schema / properties / first_tags / descriptionRemoved value: -"Top-level rank category tags."Output schema / titleRemoved value: -"RankCategoriesResponse"v0.5.6Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "RankFirstTag": {
+ "properties": {
+ "key": {
+ "description": "Category key.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "description": "Display name.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "second_tags": {
+ "description": "Sub-categories. Pass a `second_tags[].key` to `rank_list`.",
+ "items": {
+ "$ref": "#/$defs/RankSecondTag"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "RankSecondTag": {
+ "properties": {
+ "key": {
+ "description": "Tab key to pass to `rank_list` (e.g. \"hot_all-us\").",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "market": {
+ "description": "Market this tab covers, e.g. \"US\" / \"HK\".",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "description": "Display name.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ }
+ },
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "description": "Returned by `rank_categories`. Wraps a `first_tags` array of rank tab\ncategory configurations for the popularity leaderboard. Subset of the wire\nresponse.",
+ "properties": {
+ "first_tags": {
+ "description": "Top-level rank category tags.",
+ "items": {
+ "$ref": "#/$defs/RankFirstTag"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ }
+ },
+ "title": "RankCategoriesResponse",
+ "type": "object"
+}v0.4.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds context about the popularity leaderboard but no additional behavioral traits beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. Front-loaded with the main purpose, and the second sentence provides a relevant usage hint.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and an output schema (not shown), the description sufficiently explains the tool's purpose and provides relevant context about its usage in relation to rank_list.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage. Per baseline guidelines, score is 4. Description does not need to add parameter info as none exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies the verb 'Get' and the resource 'rank tab category configurations for the popularity leaderboard'. It distinguishes this tool from the sibling 'rank_list' by indicating the data flow between them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage by mentioning passing a second_tags key to rank_list, but does not explicitly state when to use this tool versus alternatives or provide exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server