Skip to main content
Glama

glim.sh

by sh.glim
OverviewDiscussionsAdmin

Twitter Search

glim_twitter_search
Read-onlyIdempotent

Search Twitter/X. Returns a compact human-readable list by default; pass format='json' for full structured data. Use glim_twitter_get(ref) for full thread context. Use docs://search-operators for reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort by relevance or recency: "top" (most engaged tweets matching the query - best for "what's the conversation about X") or "latest" (newest first - best for monitoring/recency). Default: "top".
queryYesSearch query with operators (e.g. 'from:elonmusk AI min_faves:100 within_time:7d')
cursorNoPagination cursor from previous search. Ranking is strongest on page 1 - paged results under sort:'top' trend toward recency (upstream behavior).
formatNoOutput format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.text
end_dateNoOnly tweets before this time. YYYY-MM-DD (inclusive through end of day UTC) or ISO 8601 datetime with Z/offset (e.g. 2026-04-13T14:30:00Z)
start_dateNoOnly tweets on or after this time. YYYY-MM-DD (UTC midnight) or ISO 8601 datetime with Z/offset (e.g. 2026-04-13T14:30:00Z)
expand_urlsNoWhen true, auto-crawl entity URLs and attach crawled_content to tweets. Off by default: responses can grow by up to 4KB per expanded URL. Use glim_web_fetch(url) for targeted crawls instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor from previous search"New value: +"Pagination cursor from previous search. Ranking is strongest on page 1 - paged results under sort:'top' trend toward recency (upstream behavior)."
  2. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"Sort by recency or popularity: \"latest\" (newest first) or \"top\" (most engaged). Default: \"latest\"."New value: +"Sort by relevance or recency: \"top\" (most engaged tweets matching the query - best for \"what's the conversation about X\") or \"latest\" (newest first - best for monitoring/recency). Default: \"top\"."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior; description adds clarity on default output format and the effect of the format parameter. No contradictions.

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 targeted sentences, each adding unique value: action, format guidance, and cross-references. No redundancy.

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?

Provides enough context for an agent to understand usage and output variability, but lacks explicit output structure details (mitigated by format options). Cursor pagination behavior is noted in schema but not in description.

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 description coverage is 100% with detailed parameter descriptions. Description adds context on output format defaults and cross-references, but does not significantly expand on schema descriptions.

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?

Clearly states 'Search Twitter/X' as the primary action, distinguishes from sibling tool glim_twitter_get for full thread context, and mentions output format options.

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

Usage Guidelines5/5

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

Explicitly advises when to use glim_twitter_get for thread context, references search operators documentation, and hints at format selection based on use case.

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

All glim.sh toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources