Upload-Post

Official

Overview Schema Source Related Servers Discussions Admin

Generate platform-integration JWT

generate_jwt

Generate a JWT and connection URL so end users can connect social media accounts inside an embedded white-label Upload-Post flow.

Instructions

Generate a JWT + connection URL so an end-user can connect socials inside an embedded Upload-Post flow (white-label integration).

Input Schema

TableJSON Schema

Name	Required	Description
`language`	No	Force the connection page language for this profile. When omitted, the page auto-detects the visitor's browser language and falls back to English.
`uiLabels`	No	Flat map of i18n dot-path keys to replacement strings for the connection page, e.g. { 'connect.title': 'Link your accounts' }. Max 100 entries; keys must match ^[a-zA-Z0-9_.]+$ and values are at most 300 characters. Echoed back in the `profile` object of validate_jwt.
`username`	Yes
`logoImage`	No
`platforms`	No
`redirectUrl`	No
`connectTitle`	No
`showCalendar`	No
`readonlyCalendar`	No
`connectDescription`	No
`redirectButtonText`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.11.1Sep 9, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed2 schema fields changedv0.7.0Jul 29, 2026

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "es",
-  "de",
-  "fr",
-  "pt"
-]New value: +[
+  "en",
+  "es",
+  "de",
+  "fr",
+  "pt",
+  "pl",
+  "tr"
+]

addedInput schema / properties / uiLabels

Added value: +{
+  "additionalProperties": {
+    "maxLength": 300,
+    "type": "string"
+  },
+  "description": "Flat map of i18n dot-path keys to replacement strings for the connection page, e.g. { 'connect.title': 'Link your accounts' }. Max 100 entries; keys must match ^[a-zA-Z0-9_.]+$ and values are at most 300 characters. Echoed back in the `profile` object of validate_jwt.",
+  "type": "object"
+}

First observedv0.4.0Jul 16, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations provide only generic hints (not read-only, not destructive, not open-world). The description adds that the tool returns a JWT and connection URL and is used in an embedded flow, but doesn't disclose side effects such as token expiration, session creation, or whether it persists state. This is acceptable for a token-generation tool but leaves behavioral details to the agent's assumptions.

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 with no filler; the core action and purpose are front-loaded. It earns its place without redundancy.

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?

Despite an output schema and nested objects, the description is too thin for an 11-parameter tool with 18% coverage. It omits prerequisites (e.g., username), how to select platforms, or how the returned URL is used, so an agent would struggle to construct a correct call beyond the single required parameter.

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

Parameters2/5

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

With only 18% schema description coverage, most parameters (username, platforms, redirectUrl, etc.) are undocumented in the schema, and the description adds no parameter-level meaning. It only hints at the high-level purpose (connecting socials), so the agent has no guidance for the many undefined parameters.

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 states a specific action ('Generate a JWT + connection URL') with a concrete resource and purpose (letting an end-user connect socials in an embedded Upload-Post flow). It clearly distinguishes this from sibling validate_jwt and upload_* tools by positioning it as token generation for a white-label integration.

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 gives a clear intended-use context: it is for end-users connecting socials inside an embedded white-label Upload-Post flow. However, it doesn't explicitly contrast with validate_jwt or state when not to use it, leaving some routing to inference.

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

Deploy Server