Skip to main content
Glama

CryptoSocials

by net.cryptosocials.api
OverviewDiscussionsAdmin

Search posts

search_posts
Read-only

Use when finding what Crypto Voices said about an asset or topic before, during or after a period of interest. Search stored posts in a bounded UTC window; returns text previews, source links, IDs and observed metrics. Use order=time_balanced for discussion across the period; get_post/get_posts verify selected full retained text. Set detail=market for capture-price context. No live X search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoExplore retains up to 500 matches. Exhaustive retains every match for an accepted scope up to 5000; larger scopes fail explicitly so you can partition dates. Continuations last 30 minutes.explore
textNo
limitNoPage size: an integer from 1 to 50, default 20. Read additional pages with the returned cursor and unchanged query/page size.
orderNotime_balanced interleaves seven equal parts of the requested period before the retention limit; useful for broad discussion research, not statistical sampling.newest
cursorNoPass the returned next_cursor unchanged to the same tool and connection with the original query arguments. For post searches preserve exact UTC dates, filters, order, limit, projection and mode. Omit cursor to start a new or changed query.
detailNoCompact reading evidence by default. Choose market to include full stored capture and publication-price provenance for every post.compact
date_toYesExclusive UTC end; required.
asset_idsNoCanonical asset IDs from resolve_assets, not tickers or provider IDs.
chain_idsNoCoin chain IDs, e.g. solana, ethereum, base, robinhood. Includes confirmed stored V1, native and multichain associations; candidates, expired and unknown associations are excluded. Posts qualify through their attached coins.
date_fromYesInclusive UTC start; required. Maximum window 366 days.
has_mediaNo
asset_typeNoKnown asset relationship. With chain_ids, type must match on one of those chains; native and token relationships may coexist across chains. Unknown has no classified relationship.
author_idsNoCanonical author IDs from search_authors, not X handles or user IDs.
multichainNoTrue selects assets with at least two known chains. False means fewer than two KNOWN chains, not proven single-chain.
post_typesNo
projectionNoindex omits text; preview returns short text; reading returns full retained text and relations without prices; market includes price evidence.
evidence_classNoFilter standalone collected evidence versus retained embedded quote evidence; omitted includes both.
exclude_post_typesNoExclude selected types; excluding original also excludes historical unknown labels, while excluding repost keeps ordinary unknown labels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Page size: an integer from 1 to 50, default 20. Read additional pages with the returned cursor and unchanged query/page size."
  2. Changed1 schema field changed
    • addedInput schema / properties / text / properties / full_text_query / description
      Added value: +"Space-separated AND, spaced OR, quoted phrases and minus exclusions. No stemming: agent and agents differ. Unquoted parentheses unsupported; repeat common terms, e.g. AI agent OR AI agents."
  3. Changed2 schema fields changed
    • addedInput schema / properties / asset_ids / description
      Added value: +"Canonical asset IDs from resolve_assets, not tickers or provider IDs."
    • addedInput schema / properties / author_ids / description
      Added value: +"Canonical author IDs from search_authors, not X handles or user IDs."
  4. Changed1 schema field changed
    • changedInput schema / properties / exclude_post_types / description
      Previous value: -"Exclude only known types; excluding repost keeps unknown types."New value: +"Exclude selected types; excluding original also excludes historical unknown labels, while excluding repost keeps ordinary unknown labels."
  5. Changed1 schema field changed
    • addedInput schema / properties / cursor / description
      Added value: +"Pass the returned next_cursor unchanged to the same tool and connection with the original query arguments. For post searches preserve exact UTC dates, filters, order, limit, projection and mode. Omit cursor to start a new or changed query."
  6. 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 readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: it discloses the return shape (text previews, source links, IDs, observed metrics) and the bounded/stored-vs-live nature of the search. It omits auth/rate-limit context, and mode/cursor behavior lives only in the schema, so it stops short of 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.

Conciseness5/5

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

Front-loaded with the trigger, then purpose, then targeted parameter pointers, then the boundary condition. Every clause earns its place and no sentence is filler, even though the description is dense.

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?

For an 18-parameter tool with no output schema, the description supplies the essentials: purpose, main routing alternatives, approximate return contents, and the live-search limitation, while 83% schema coverage fills in the rest. It leaves mode/pagination semantics entirely to the schema, which is a minor gap.

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 83%, well above the threshold where the schema carries the load, so baseline 3. The description still adds usage-oriented meaning for two key params (order=time_balanced for broad discussion, detail=market for capture-price context), which is more than merely restating the schema.

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?

States a specific verb and resource ('Search stored posts in a bounded UTC window') and adds scope ('Crypto Voices', UTC-bounded). It distinguishes itself from get_post/get_posts (full-text verification) and from live tools ('No live X search'), so an agent can separate it from all siblings.

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?

Opens with an explicit when-to-use trigger ('finding what Crypto Voices said... before, during or after a period of interest'), routes to alternatives (get_post/get_posts for retained full text) and gives an explicit exclusion ('No live X search'). Nothing about selection is left to inference.

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

All CryptoSocials 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