Skip to main content
Glama
Sign In

CryptoSocials

by net.cryptosocials.api
OverviewDiscussionsAdmin

Search authors

search_authors

Find stored author candidates by platform user ID, handle prefix or display name. Historical names and uncertain matches remain explicit. An exact missing handle can be recorded locally for coverage review; no provider fetch or promise of addition.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size: an integer from 1 to 50, default 20. Read additional pages with the returned cursor and unchanged query/page size.
queryYesX handle such as @CryptoKaleo, platform user ID or stored display-name prefix. Exact missing handles may record local coverage demand.
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.
request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_id
      Added value: +{
+  "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+  "type": "string"
+}
  2. 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."
  3. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"X handle such as @CryptoKaleo, platform user ID or stored display-name prefix. Exact missing handles may record local coverage demand."
  4. 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."
  5. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The description explains why readOnlyHint is false: an exact missing handle may be recorded locally for coverage review. That is genuine context beyond the annotations, and 'no provider fetch or promise of addition' sets accurate expectations about side effects and guarantees.

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?

Three sentences, front-loaded with the lookup keys and behaviour. The final clause ('no provider fetch or promise of addition') is telegraphic but earns its place by bounding expectations.

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?

There is no output schema and the description never indicates what a result looks like (candidate fields, match certainty, next_cursor). Pagination is covered only by the schema, leaving the return contract underspecified.

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 75%, so limit, cursor and request_id are already documented in the schema. The description restates the query forms but adds nothing new about pagination, limits or the request_id correlation parameter.

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 (Find) and resource (stored author candidates) plus the three lookup keys: platform user ID, handle prefix, display name. 'Stored' implicitly separates it from live-fetch siblings like get_profile, but no sibling is named.

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 is implied by the lookup modes, and the tool explains the exact-missing-handle case, but it never states when to prefer this over get_profile or resolve_assets, nor when not to use it.

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