Skip to main content
Glama
ScrapingBot MCP Server

ScrapingBot MCP Server

by sostag

Scrape a social media page

scrape_social_media
Read-only

Scrape a public social media profile, post or search (Instagram, TikTok, Facebook, LinkedIn, X/Twitter, Threads). Always use this tool for these networks, never scrape_raw_html.

Instructions

Scrape a public social media profile, post or search (Instagram, TikTok, Facebook, LinkedIn, X/Twitter, Threads). Always use this tool for these networks, never scrape_raw_html. Choose the scraper and give its inputs: instagramProfile (account (name or profile URL); returns the 12 latest posts), instagramPost (url), tiktokProfile (url), tiktokHashtag (hashtag; max_video_count), facebookProfile (url (page or personal profile, without its posts)), facebookPost (url), facebookOrganization (url), facebookMarketplaceItem (url; country), facebookMarketplaceSearch (keyword, city, country; items_limit), linkedinProfile (url; language), linkedinCompanyProfile (url; language), linkedinPost (url), linkedinSearchResult (keywords; page, language), twitterProfile (url; number_of_tweets), twitterSearch (search; posts_max_count), threadsProfile (url), threadsPost (url). Waits for the result for about a minute, otherwise returns a responseId for get_social_media_result: use that tool to wait longer, as calling this one again is billed again. Costs 30 credits; failed requests are refunded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scraper": "<scraper>"
    },
    "name": "scrape_social_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoProfile, post or page URL
cityNo
pageNo
searchNotwitterSearch
accountNoinstagramProfile: account name or profile URL
countryNo
hashtagNo
keywordNofacebookMarketplaceSearch
scraperYes
keywordsNolinkedinSearchResult
languageNo
items_limitNo
max_video_countNo
posts_max_countNo
number_of_tweetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.1
    • removedInput schema / properties / load_more_items_count
      Removed value: -{
      -  "exclusiveMinimum": 0,
      -  "type": "integer"
      -}
  2. Changed1 schema field changedv1.0.1
    • removedInput schema / properties / posts_number
      Removed value: -{
      -  "exclusiveMinimum": 0,
      -  "type": "integer"
      -}
  3. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds the cost (30 credits), the refund policy on failures, the ~1 minute wait before an async responseId is returned, the double-billing risk on retry, and a concrete return shape for instagramProfile (12 latest posts). This is substantive behavior beyond the structured fields.

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?

Purpose and the scrape_raw_html exclusion are front-loaded, then the per-scraper input table, then the async/cost caveats — a sensible order. The middle enumeration is a single dense run-on that is harder to scan than a list, but nearly every clause carries information the schema does not.

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 17-variant, 15-parameter tool with no output schema, the description covers routing, per-variant inputs, timing, async handoff, cost, and refunds. Nothing an agent needs in order to call it correctly and handle the slow path is missing.

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 only 33% across 15 parameters, and the description compensates well by mapping each scraper enum value to its own inputs (e.g. facebookMarketplaceSearch takes keyword, city, country, items_limit). It stops short of stating that only 'scraper' is required and that non-applicable parameters should be omitted, and 'page' and generic 'url' semantics remain thin.

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 (scrape) plus resource (public social media profile, post, or search) and enumerates the covered networks. It directly names the sibling it must not be confused with (scrape_raw_html), so an agent can route between the two without inspecting either schema.

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?

Explicit exclusion: 'Always use this tool for these networks, never scrape_raw_html.' It also gives the follow-up rule for slow calls (use get_social_media_result rather than re-calling, because re-calling is billed again), which is exactly the alternative-selection guidance an agent needs.

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