Skip to main content
Glama

SocialCrawl

by io.github.RidioDevelopment
OverviewAdmin

SocialCrawl API Self-Discovery (utility endpoints)

socialcrawl_discover
Read-onlyIdempotent

The API describing itself, live, at 0 credits — the /v1/utility/* family. 'quickstart': everything needed for a first successful call (auth, base URL, response envelope, billing model, the full error taxonomy, rate limits, paging). 'catalog': every endpoint with its live metered-aware price, params, and paging flag — filter by platform/search/method. 'endpoint': one endpoint's complete usage guide — every parameter with type and example, the exact pricing rule, cache TTL, paging recipe, an example response, a copy-paste curl, and related endpoints. 'llms': the agent context corpus for the whole API or one platform. 'freshness': compare the live registry against this server's bundled catalogue to check whether this MCP version has fallen behind the API. 'status': every platform's live circuit-breaker state from the public GET /v1/status meta route — read it before retrying a persistent 502/503, since a degraded platform is the breaker holding traffic off a failing upstream. These answer from the live registry at request time, so unlike bundled data they can never drift from what is actually callable — use them when correctness matters more than latency, or when an endpoint looks unknown. Without an API key everything except 'llms' still answers from bundled data ('status' needs no key at all).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoendpoint (required): the endpoint id as 'platform/resource' (e.g. 'tiktok/profile'), a path ('/v1/tiktok/profile'), or a full URL.
liveNoSet false to answer from this server's bundled catalogue instead of calling the live API. Default is live whenever an API key is configured; without a key everything except 'llms' falls back to bundled data automatically.
pageNoPage number (default 1). Long output is paged, not truncated.
actionNo'quickstart' (default): auth, base URL, envelope, billing, the error taxonomy, limits, and a first call — GET /v1/utility/quickstart. 'catalog': the machine-readable list of every endpoint with live metered-aware prices — GET /v1/utility/endpoints. 'endpoint': one endpoint's complete usage guide, params, pricing rule, cache, paging, example response, curl, and related endpoints — GET /v1/utility/endpoint. 'llms': the agent context corpus for the whole API or one platform — GET /v1/utility/llms. 'freshness': compare the live registry against this server's bundled catalogue to see whether this MCP version is current. 'status': every platform's live circuit-breaker state — GET /v1/status, the public meta route to read before retrying a persistent 502 or 503.
formatNollms: 'markdown' (default) returns the corpus text; 'json' returns a structured context object.
methodNocatalog: filter by HTTP method. endpoint: disambiguate a resource registered under more than one method (the stateful `web` family).
searchNocatalog: case-insensitive substring filter over endpoint paths and summaries.
platformNoScope to one platform slug (e.g. 'tiktok'). Applies to quickstart, catalog, and llms.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds substantial context beyond those: live registry answers avoid drift, bundled fallback behavior without an API key, status requiring no key, zero-credit utility access, and paged rather than truncated output. This richly discloses operational behavior without contradicting the annotations.

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?

The description is long but organized around the six action modes, and it front-loads the core purpose: the API describing itself live at zero credits. Every sentence contributes useful behavioral or usage context, though the density makes it somewhat heavy as a single block.

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

Completeness5/5

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

Despite having no output schema, the description explains what each action returns, including quickstart content, catalog format, endpoint guides, llms corpus options, freshness comparison, and status circuit-breaker data. It also covers auth fallback, paging behavior, and billing context, making the tool effectively self-sufficient for an agent to invoke correctly.

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?

The input schema has 100% parameter coverage with detailed descriptions, including enums and per-action explanations. The description adds high-level context around live versus bundled data and when to use actions, but it does not add significant per-parameter meaning beyond what the schema already provides.

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?

The description clearly identifies the tool as live self-discovery of the SocialCrawl API at zero credits, covering the /v1/utility/* family and enumerating each action mode. It is specific about the resource and behavior, though it does not explicitly differentiate itself from sibling tools like socialcrawl_get_docs or socialcrawl_list_endpoints by name.

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

Usage Guidelines4/5

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

The description gives actionable guidance: use these live endpoints when correctness matters more than latency, when an endpoint looks unknown, and read 'status' before retrying persistent 502/503 errors. It does not explicitly name sibling alternatives or state when not to use the tool, but the context is clear enough for an agent.

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

All SocialCrawl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources