Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Get Facebook Page details (contacts, category, rating)

get_facebook_pages
Read-onlyIdempotent

Public details of Facebook Pages by name or link: name, categories, e-mail, phone, address, websites, other social accounts, followers, likes, rating and review count, price range, services and verified badge. No login.

Instructions

Public details of Facebook Pages by name or link: name, categories, e-mail, phone, address, websites, other social accounts, followers, likes, rating and review count, price range, services and verified badge. No login. Useful for lead lists, local business research and enriching company records. Posts are not included. Runs the Apify Actor tacps126/facebook-pages on your Apify account (about $0.003 per page; spend per call is capped at $0.5).

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": {
      "pages": "<pages>"
    },
    "name": "get_facebook_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYesPage names or links, e.g. ["katzsdeli", "https://www.facebook.com/nasa"].
max_itemsNoMaximum results to return (default 50, max 1000). Cost scales with this.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations it discloses no-login auth, the specific backing Actor (tacps126/facebook-pages), per-page pricing (~$0.003) and a hard per-call spend cap ($0.5). That cost and scope disclosure is exactly the context an agent needs before invoking a paid open-world scrape.

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?

Roughly two dense sentences: returned fields first, then usage and cost. Every clause carries information, though the long field enumeration could be trimmed slightly given an output schema exists.

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?

Output schema exists, so return values need not be explained, yet the description still frames the result surface while covering auth, cost, exclusions, and pagination limits. Nothing an agent needs to call this correctly 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 100%, so the baseline is 3; the description still adds meaning by restating that pages accept names or links and by tying cost to result volume, which reinforces the max_items semantics. It does not explain the advanced extra_input merge beyond what the schema says.

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 and resource ('Public details of Facebook Pages by name or link') and enumerates exactly what is returned (contacts, category, rating, followers, verified badge). It also carves out what is excluded ('Posts are not included'), which separates it from post-scraping alternatives, though no sibling tool by name is referenced.

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 concrete use contexts ('lead lists, local business research and enriching company records') and a key prerequisite ('No login'). It stops short of explicit when-not-to-use guidance or naming an alternative such as find_local_businesses, so routing is inferred rather than stated.

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