Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_facebook_pages_item

Retrieve one public Facebook Page contact record from the dataset by page_id, returning title, username, category, address, website, email, phones, WhatsApp, like count, and source URL.

Instructions

Get a Facebook Page from the dataset. Returns one public Facebook Page contact record from the dataset by page_id: title, username, category, address, website, email, phones, WhatsApp, like count and source URL. contact_observed_at marks when contact fields were last seen complete. A Page not in the dataset returns 404.

Input Schema

NameRequiredDescriptionDefault
page_idYesFacebook Page id, max 128 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.8/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 add real behavioral context: it discloses 404 behavior for a missing Page and explains that `contact_observed_at` marks when contact fields were last seen complete. It does not mention auth or rate limits, but for a read lookup this is solid coverage.

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?

Three sentences, front-loaded with purpose, then return contents, then the edge case. Each sentence carries distinct information and nothing is redundant.

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?

No output schema exists, so the description correctly compensates by listing the returned fields and the freshness field, plus the 404 case. It is nearly complete for a single-item lookup, missing only auth/permission notes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single `page_id` parameter is already documented in the schema (including the 128-char limit). The description adds only that the lookup is keyed on `page_id`, so baseline 3 applies.

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 ("Get a Facebook Page from the dataset") and enumerates the returned fields, making the retrieval purpose clear. It implies but never explicitly names the sibling datasets_facebook_pages_search, so sibling differentiation is left to inference.

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 is implied by the required `page_id` and the by-id framing, but there is no explicit when-to-use guidance, no note that a search call is typically needed first to obtain a page_id, and no stated exclusions.

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