Skip to main content
Glama
Sign In

Facebook Pages MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Facebook Pages Prompts

prompts_menu
Read-only

Browse the Facebook Pages prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

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": {
      "request": "<request>"
    },
    "name": "prompts_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
is_customNo
prompt_idNo
prompt_typeNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's added value is the mode semantics and the custom-vs-system prompt distinction. It says nothing about pagination, result size, or what happens when prompt_details is called without a prompt_id — gaps that matter for a catalog browser.

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?

A one-line purpose followed by a two-item numbered list; every clause conveys a distinct routing or parameter instruction, and the purpose is front-loaded. No filler.

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?

An output schema exists, so return values need not be described. With five optional parameters and only a 0%-coverage schema, the description covers the essential call shapes; only the allowed domain of prompt_type and error behavior for missing required-per-mode params are absent.

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 description coverage is 0%, so the description carries the full burden and largely meets it: it maps workspace_id + prompt_type to the menu mode, prompt_id to prompt_details, and is_custom + workspace_id to workspace lookups. It does not explain what values prompt_type accepts or what is_custom defaults to, leaving one meaningful hole.

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 first line states a specific verb and resource ('Browse the Facebook Pages prompt catalog'), which is unambiguous. Sibling tools (execute_action, query_data, query_contexts) are generic and unrelated, so no explicit differentiation is needed or given — it's clear this is the prompt-catalog reader.

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?

The numbered items effectively document the two modes: 'menu' to list, 'prompt_details' to fetch a body, with the condition that workspace prompts require is_custom=True plus workspace_id. No exclusions or failure conditions are stated, keeping it just under a 5.

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