Skip to main content
Glama
Sign In
Jotify Moment MCP Server

Jotify Moment MCP Server

by daocatt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

jotify_create_post

Publish a Moment post on Jotify Moment with Markdown text, images, videos, or audio. Provide content and optional media URLs to share updates.

Instructions

在 Jotify Moment 平台发布一条图文/音视频动态。正文支持 Markdown

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": {
      "content": "<content>"
    },
    "name": "jotify_create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesMoment 正文内容，支持 Markdown
embedIdNo
embedTypeNo
mediaUrlsNo配图/多媒体列表（可通过 upload 接口获取）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses supported media types and Markdown formatting, but does not describe the return value, post visibility, or any side effects of publishing. This is a modest disclosure for a create operation.

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 a single concise sentence in Chinese, front-loaded with the main action and without any unnecessary words. It efficiently conveys the core purpose and key features.

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?

For a create operation with no output schema, the description covers the main purpose, media types, and Markdown support, but lacks critical context such as return values, required authentication, or explanation of embedId/embedType. It is minimally viable but leaves meaningful gaps.

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?

Schema description coverage is only 50% (content and mediaUrls are described, embedId and embedType are not). The tool description adds some context for content (Markdown) and mediaUrls (media types), but completely ignores embedId and embedType, leaving them ambiguous in both schema and description.

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 action: publish an image-text/audio-video post on the Jotify Moment platform, and notes Markdown support. This specific verb+resource distinguishes it from sibling tools like upload_media and list_recent_posts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a workflow by mentioning that mediaUrls can be obtained via the upload interface, hinting at when upload tools might precede this one. However, it lacks explicit when-to-use or alternative tool guidance, leaving differentiation mostly implicit.

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