Skip to main content
Glama
Sign In

Facebook Pages MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Facebook Pages Data Query

query_data
Read-only

Execute Facebook Pages data queries (Step 3 FINAL).

Prerequisites: Run query_contexts with request='accounts' (includes available_actions) + request='actions_details' to understand the required payload.

IMPORTANT: The 'body' parameter is a dictionary that must contain ALL fields including:

  • action: Table/action name (e.g. 'posts', 'insights')

  • workspace_id: Integer workspace ID

  • brand_id: Integer brand ID

  • page_id: Page identifier

  • Any other fields from the helper response (filters, date ranges, metrics, etc.)

Do NOT pass these as separate parameters - they must ALL be inside the body dictionary.

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": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already disclose readOnlyHint=true and openWorldHint=true, and the description adds meaningful execution-flow context: this is the final step and requires a prior helper call to understand the payload. It still omits failure behavior, authentication needs, and rate limits.

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?

The description is front-loaded with the core action, then prerequisites, then the critical body-shape warning. The emphatic 'ALL fields' and 'ALL inside the body dictionary' wording is purposeful and earns its place.

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?

Given a complex nested body object and an output schema that covers return values, the description provides the essential prerequisite and payload-construction guidance. It could do more to differentiate this from execute_action, but it is otherwise complete enough to invoke correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: it lists action, workspace_id, brand_id, page_id, and additional helper-provided fields that must all be inside the body dictionary. It also explicitly warns not to pass those fields as separate parameters, which is critical for correct invocation.

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 and resource: 'Execute Facebook Pages data queries,' and marks this as 'Step 3 FINAL.' It distinguishes the tool from the query_contexts helper, though it does not explain how it differs from the sibling execute_action.

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?

It gives an explicit prerequisite: run query_contexts with request='accounts' and request='actions_details' before using this tool. However, it does not state when to prefer execute_action or any conditions under which this tool should not be used.

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

All Facebook Pages MCP by InsightfulPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources