Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_facebook_pages_facets

Get category or discovery source facet counts for the Facebook Pages dataset, with query filters to analyze and page through values.

Instructions

Facet the Facebook Pages dataset. Returns terms aggregation counts for the Facebook Pages dataset. Facet enum: category, discovery_source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over title and address, max 256 characters
sortNoSort enum: relevance, likes_desc, likes_asc, hydrated_at_desc, hydrated_at_asc
afterNoContinuation from next_after; requires order=value_asc and unchanged filters
facetYesFacet enum: category, discovery_source
limitNoFacet values per response, default 50, maximum 200
orderNocount_desc returns most common values; value_asc pages through all values
page_idNoExact Facebook Page id filter, max 128 characters
categoryNoExact Page category filter (case-insensitive), max 128 characters
has_emailNoFilter by a public contact email
has_phoneNoFilter by at least one public phone number
max_likesNoMaximum Page like count
min_likesNoMinimum Page like count
identifierNoExact Page username/identifier filter (case-insensitive), max 128 characters
has_websiteNoFilter by a linked website
has_whatsappNoFilter by a public WhatsApp contact
hydrated_afterNoRecords last refreshed on or after this date (RFC3339 or YYYY-MM-DD)
hydrated_beforeNoRecords last refreshed on or before this date (RFC3339 or YYYY-MM-DD)
discovery_sourceNoExact filter for how the Page was discovered (e.g. business_search, warc_domain_scan, wikidata), max 128 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.17.5
    • addedInput schema / properties / after
      Added value: +{
+  "description": "Continuation from next_after; requires order=value_asc and unchanged filters",
+  "type": "string"
+}
    • addedInput schema / properties / facet / enum
      Added value: +[
+  "category",
+  "discovery_source"
+]
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Facet values per response, default 50, maximum 200",
+  "type": "integer"
+}
    • addedInput schema / properties / order
      Added value: +{
+  "description": "count_desc returns most common values; value_asc pages through all values",
+  "enum": [
+    "count_desc",
+    "value_asc"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "likes_desc",
+  "likes_asc",
+  "hydrated_at_desc",
+  "hydrated_at_asc"
+]
  2. Addedv1.16.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that this returns terms aggregation counts, which is useful, but it doesn't mention pagination behavior (the 'after' parameter requires order=value_asc and unchanged filters), the default limit of 50, or that the response is a facet breakdown rather than records. The description is minimal and leaves the agent to infer behavior from the schema.

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?

Two sentences, no filler, and the key information (facet enum values) is front-loaded. It's appropriately sized for a simple facet tool, though it could have used the space to add behavioral context like pagination.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter tool with no annotations and no output schema, the description is thin. It doesn't explain the continuation/pagination mechanism, the meaning of 'order' values, or what the response structure looks like. The schema covers parameter definitions, but the description doesn't provide the operational context an agent needs to use this tool effectively, such as how to page through all facet values.

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 description coverage is 100%, so the schema already documents all 18 parameters. The description adds the facet enum values and the concept of terms aggregation counts, which gives context for the 'facet' parameter. However, it doesn't explain the relationship between 'after' and 'order' (continuation requires order=value_asc), which is a meaningful semantic gap that the schema alone doesn't fully clarify.

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?

The description states a specific verb ('Facet') and resource ('the Facebook Pages dataset'), and lists the two facet enums. It clearly identifies this as an aggregation/counts tool rather than a search or item retrieval tool. However, it doesn't explicitly distinguish itself from sibling tools like datasets_facebook_pages_search or datasets_facebook_pages_item, though the facet terminology is fairly distinctive.

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?

The description implies usage: use this when you want terms aggregation counts for the Facebook Pages dataset. It doesn't explicitly say when NOT to use it or name alternatives like datasets_facebook_pages_search for full-text search or datasets_facebook_pages_item for record details. The facet enum hints at the use case but doesn't provide routing guidance.

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