Skip to main content
Glama

SocialCrawl

by io.github.RidioDevelopment
OverviewDiscussionsAdmin

SocialCrawl Pricing & Credit Costs

socialcrawl_pricing
Read-onlyIdempotent

Exact credit pricing for every one of the 575 SocialCrawl endpoints. 'overview' returns the tier ladder (329 standard / 211 advanced / 35 premium), every free endpoint, every flat override, all 71 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". 'hydration' catalogues every opt-in include= row join — what each fills, its per-row rate, its row cap, and what a fully-joined page holds. On 'endpoint', pass the include (and rows) you intend to send and the band becomes the exact upfront hold, itemised per join. Use this before spending credits. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsNoendpoint: the row cap you intend to send alongside `include` (the endpoint's own `limit`). A row join holds per row, so capping the rows caps the credits — quote it before you spend it.
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, row joins, and worst case (needs platform + resource) — add `include`/`rows` for an exact quote instead of a band. 'platform': the cost table for one platform (needs platform). 'list': rank/filter endpoints by price across platforms. 'hydration': every `include=` row join in the API, what each one fills, what it costs per row and what a fully-joined page holds (optionally scoped with `platform`).
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.
includeNoendpoint: the `include=` row-join tokens you intend to send (comma-separated, e.g. 'engagement' or 'engagement,channel'). Turns the quoted band into the exact hold for that call, itemised per join. Costs nothing to ask.
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.

  1. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"'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."New value: +"'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, row joins, and worst case (needs platform + resource) — add `include`/`rows` for an exact quote instead of a band. 'platform': the cost table for one platform (needs platform). 'list': rank/filter endpoints by price across platforms. 'hydration': every `include=` row join in the API, what each one fills, what it costs per row and what a fully-joined page holds (optionally scoped with `platform`)."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "overview",
-  "endpoint",
-  "platform",
-  "list"
-]New value: +[
+  "overview",
+  "endpoint",
+  "platform",
+  "list",
+  "hydration"
+]
    • addedInput schema / properties / include
      Added value: +{
+  "description": "endpoint: the `include=` row-join tokens you intend to send (comma-separated, e.g. 'engagement' or 'engagement,channel'). Turns the quoted band into the exact hold for that call, itemised per join. Costs nothing to ask.",
+  "type": "string"
+}
    • addedInput schema / properties / rows
      Added value: +{
+  "description": "endpoint: the row cap you intend to send alongside `include` (the endpoint's own `limit`). A row join holds per row, so capping the rows caps the credits — quote it before you spend it.",
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces with 'No API key required' and 'Costs nothing to ask' — useful context beyond the annotation bar. It explains the metered ceiling-then-refund mechanic, which is genuine behavioral detail. No rate limits or error behavior disclosed, keeping it off 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.

Conciseness4/5

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

Front-loaded with the core purpose, then action-by-action detail plus a workflow hint. Dense but well-organized; only mild redundancy between the description and the `action` enum prose keeps it from a 5.

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 a 12-param, 5-action read-only pricing tool with no output schema, the description covers action selection, parameter interaction, and the cost-quoting workflow completely. Missing only the shape of returned data, but output_schema absence makes that 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 100% so baseline is 3, but the description adds cross-parameter semantics: how `include`+`rows` convert a band into an exact hold, what `endpoint` requires (platform+resource), and how `method` disambiguates the web platform. This meaningfully exceeds the schema's field-by-field docs.

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 verb+resource — exact credit pricing across 575 endpoints — and enumerates the five actions with their distinct outputs. The distinction from siblings (check_balance, list_endpoints) is implicit but strong: this is the cost-quoting tool, not a balance reader or endpoint lister.

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 instructs 'Use this before spending credits', names the intended workflow (pass `include`/`rows` to turn a band into an upfront hold), and provides concrete usage examples like 'everything I can call for 1 credit'. When-to-use and how-to-use are both covered.

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