Skip to main content
Glama
Sign In
Spectre

Spectre

by pranrichh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_user_likes

Retrieve a user's liked tweets by providing their numeric user ID. Optionally set a limit on the number of tweets returned.

Instructions

Get a user's liked tweets.

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": {
      "user_id": "<user_id>"
    },
    "name": "get_user_likes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax tweets to return (default 20, max 100).
user_idYesThe numeric user ID.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

C2.9/5.0
Behavior1/5

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

No annotations provided, and the description does not disclose any behavioral traits beyond the basic function (e.g., pagination, rate limits, authentication, or side effects). The agent learns nothing about the tool's behavior beyond its name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (one sentence) but lacks structure. It is not verbose, but the brevity comes at the cost of omitting important usage and behavior information. Acceptable for minimal viability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with complete schema coverage and an output schema present, the description is minimally adequate. However, it does not explain how the tool fits among many similar user-focused sibling tools.

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 baseline is 3. The description does not add any parameter meaning beyond what the schema already provides (e.g., user_id is numeric, limit has default/max). No enrichment.

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 is a concise verb+resource statement: 'Get a user's liked tweets.' It clearly distinguishes from sibling tools like get_user_tweets (user's own tweets) and get_user_media (user's media).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as get_user_tweets or get_favorites. The description does not indicate prerequisites, limitations, or context for usage.

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

Deploy Server

Other Tools