Skip to main content
Glama

SocialCrawl

by io.github.RidioDevelopment
OverviewAdmin

SocialCrawl Pricing & Credit Costs

socialcrawl_pricing
Read-onlyIdempotent

Exact credit pricing for every one of the 572 SocialCrawl endpoints. 'overview' returns the tier ladder (327 standard / 210 advanced / 35 premium), every free endpoint, every flat override, all 41 metered endpoints with their min-max band and exact charging rule, cache TTLs, and the full refund matrix. 'endpoint' gives one endpoint's price, metered rule, price-driving parameters, paging cost, and worst case. 'platform' gives a platform's whole cost table. 'list' ranks and filters endpoints by cost (maxCost/minCost/model/search/sort) — e.g. "everything I can call for 1 credit" or "the most expensive endpoints". Use this before spending credits. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNolist: sort order (default 'cost_desc' — most expensive first).
limitNolist: maximum rows to return (1-200, default 40).
modelNolist: filter by billing model — 'ladder' (tier rate per request), 'flat' (per-endpoint override), 'metered' (query-dependent, ceiling deducted then refunded down), or 'free' (0 credits).
actionNo'overview' (default): the tier ladder, every free endpoint, every flat override, every metered band with its rule, cache TTLs, and the refund matrix. 'endpoint': one endpoint's exact price, metered rule, price-driving params, and worst case (needs platform + resource). 'platform': the cost table for one platform (needs platform). 'list': rank/filter endpoints by price across platforms.
methodNoHTTP method. Disambiguates the `web` platform, where one resource is served by several methods; also filters the 'list' action.
searchNolist: free-text filter over platform, resource, summary, and archetype.
maxCostNolist: only endpoints that can cost at most this many credits (metered judged by their ceiling).
minCostNolist: only endpoints that cost at least this many credits (metered judged by their floor).
platformNoPlatform slug. Required for 'endpoint' and 'platform' actions; filters the 'list' action.
resourceNoResource path for the 'endpoint' action (e.g., 'profile', 'comments', 'jobs/{job_id}').

Schema Changelog

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

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark it read-only and idempotent; the description adds meaningful context: no API key required, output includes cache TTLs and the refund matrix, and list evaluation rules for metered costs. It does not discuss staleness or rate limits, but those are minor given 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.

Conciseness5/5

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

Dense and front-loaded: first sentence states the tool's exact scope, then each action's deliverable is listed, ending with an example. Every sentence earns its place; no filler or tautology.

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?

For a complex 10-parameter, 4-action tool with no output schema, the description covers every action mode, the contents returned by each, auth requirements, and representative use cases. The parameter schema handles the remaining syntax details.

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 100% with thorough parameter descriptions, so baseline is 3. The description adds value by grouping actions, noting that endpoint/platform actions require the platform parameter, stating the default action is 'overview', and giving real query examples.

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 precise purpose: exact credit pricing for all 572 endpoints, and enumerates four actions with exact outputs. This clearly separates it from sibling tools like socialcrawl_request or socialcrawl_check_balance.

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?

Gives clear usage context ('Use this before spending credits') and concrete query examples for the list action. It does not explicitly name sibling alternatives or state when not to use it, so it falls just short of a 5.

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