Skip to main content
Glama
Sign In
upload-post-mcp

upload-post-mcp

by MrSagarShah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Facebook pages / LinkedIn pages / Pinterest boards

list_page_targets

Retrieve platform-specific posting targets including Facebook pages, LinkedIn organization pages, and Pinterest boards for use in post scheduling.

Instructions

List posting targets needed for platform-specific IDs: facebook → pages (facebook_page_id), linkedin → organization pages (target_linkedin_page_id), pinterest → boards (pinterest_board_id).

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": {
      "platform": "<platform>"
    },
    "name": "list_page_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoUpload-post profile identifier. Omit to list across all connected accounts.
platformYesWhich targets to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 full burden. It does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or response format. The agent cannot infer side effects or safety from the description alone.

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?

Single sentence, front-loaded with verb, every word is informative. No redundancy or unnecessary detail.

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

Completeness3/5

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

The description explains the tool's purpose and mapping but lacks details on output format, error handling, or prerequisites. Given no output schema, completeness is moderate.

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% with clear parameter descriptions. The description adds little value beyond echoing the parameter mappings; it does not provide additional syntax or constraints. Baseline of 3 is appropriate.

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 clearly states the verb 'List' and the resource 'posting targets' with platform-specific mappings (facebook pages, linkedin organization pages, pinterest boards). It distinguishes from sibling tools which perform different actions like cancel, edit, or post.

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 description implies usage context by stating the tool is needed for obtaining platform-specific IDs, but does not explicitly mention when not to use it or provide alternatives. It effectively guides when to use among siblings.

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