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

upload-post-mcp

by MrSagarShah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Generate social-account connect link

generate_connect_link

Create a secure URL to link social accounts (TikTok, Instagram, X, LinkedIn) to a profile. Open the link in a browser to connect each platform.

Instructions

Generate a secure URL where social accounts (TikTok, Instagram, X, LinkedIn...) can be linked to a profile. Open it in a browser and log in to each platform.

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": {
      "username": "<username>"
    },
    "name": "generate_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesProfile identifier to connect accounts for.
platformsNoLimit which platforms are shown on the connection page. Defaults to all.
redirect_urlNoURL to redirect to after linking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided; description notes the action is generating a URL for manual login, but lacks details on URL expiration, security, or side effects.

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?

Two succinct sentences that convey purpose and usage without excess words. Front-loaded with key information.

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?

With no output schema or annotations, the description covers the core functionality adequately. Missing some edge details but acceptable for a simple URL-generation tool.

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?

All parameters have schema descriptions (100% coverage); description adds context like default platforms and the linking workflow, enhancing meaning beyond schema.

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?

Description explicitly states it generates a secure URL for linking social accounts (TikTok, Instagram, etc.) to a profile, clearly distinguishing it from sibling tools like posting or scheduling.

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?

Mentions to open URL in a browser and log in, implying manual use. Does not explicitly contrast with alternatives, but the distinct purpose makes usage context clear.

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