Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_profile

Fetch a public Facebook page's signed-out profile details—follower counts, contact info, category, photos, and Ad Library page ID—to verify or enrich page data.

Instructions

facebook: Profile. GET /v1/facebook/profile. Get a public Facebook page's profile, as a signed-out visitor sees it: id, name, adLibrary.pageId (the id the Ad Library uses), exact followerCount and talkingAboutCount, category, intro, address, phone, email, website, services, price range, rating, and the cover and profile photos. adLibrary.adStatus, creationDate and businessHours are not on the signed-out page and are omitted; likeCount appears only when the page Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "url": "<url>"
    },
    "name": "facebook_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the public Facebook page (facebook.com/<name>, profile.php?id= or /people/<name>/<id>)
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.
get_business_hoursNoAccepted for compatibility and ignored: opening hours are not on the signed-out page.
include_gated_profileNoAccepted for compatibility and ignored: gated and age-restricted pages need a login and fail at 0 credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses which fields are omitted because they are not on the signed-out page (adLibrary.adStatus, creationDate, businessHours), that likeCount is conditional, and a detailed billing model (success costs 1 credit; errors, blocked/timed-out, invalid requests and cache hits cost nothing). The only deduction is a corrupted clause — 'likeCount appears only when the page Costs 1 credit when it succeeds' — where a sentence fragment appears to have been spliced in, leaving the exact likeCount condition ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The endpoint and the core purpose are front-loaded, and the field list is dense but informative. However, the run-on final sentence is garbled and mixes two unrelated topics (likeCount availability and credit pricing), which costs clarity; splitting or repairing it would make the definition materially cleaner.

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 single-required-parameter read tool with no output schema and no annotations, the description supplies what an agent needs: the return field set, the deliberately omitted fields, the signed-out limitation, and the full cost/charging model. Nothing essential for correct invocation is missing beyond the garbled likeCount clause.

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, but the description adds real meaning beyond it: it explains that get_business_hours is inert because opening hours are absent from the signed-out page and that include_gated_profile is inert because gated/age-restricted pages require login and fail at 0 credits. It also clarifies the significance of adLibrary.pageId as 'the id the Ad Library uses', which helps an agent chain to the adLibrary siblings.

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?

The description opens with a specific verb and resource — 'Get a public Facebook page's profile, as a signed-out visitor sees it' — and then enumerates the exact returned fields (id, name, adLibrary.pageId, followerCount, category, photos, etc.). That field inventory makes it distinguishable from facebook_profile_posts, facebook_profile_events and the adLibrary siblings without opening any schema.

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

Usage Guidelines3/5

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

Usage context is implied by 'as a signed-out visitor sees it' and the credit/cost rules, which tell an agent this is a paid read that is free on error or cache hit. However, there is no explicit when-to-use versus alternatives guidance and no named sibling to route to (e.g. posts vs profile).

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

Deploy Server

Other Tools