Skip to main content
Glama
Sign In
mcp-csdn-publisher

mcp-csdn-publisher

by Ln129402
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

login

Authenticate to CSDN by providing your browser cookie to enable blog publishing.

Instructions

设置 CSDN Cookie 以完成认证。从浏览器开发者工具复制 Cookie 字符串。

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": {
      "cookie": "<cookie>"
    },
    "name": "login"
  }
}

Input Schema

NameRequiredDescriptionDefault
cookieYes从浏览器复制的 CSDN Cookie 字符串

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 discloses that it sets a cookie for authentication, but does not describe side effects (e.g., session creation, invalidation of previous session), error handling for invalid cookies, or any rate limits. Minimal behavioral context.

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 sentences, front-loaded with purpose, followed by a clear instruction. No extraneous words; every sentence earns its place.

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?

For a simple authentication tool with one parameter and no output schema, the description is sufficient. It explains the tool's purpose and parameter source. Could mention expected outcome (e.g., sets session), but adequate overall.

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 coverage is 100%, and the description for the 'cookie' parameter adds real-world context: '从浏览器复制' (copy from browser). This adds value beyond the schema's generic description, guiding the user on how to obtain the value.

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 '设置' (set) and resource 'CSDN Cookie' with purpose '完成认证' (complete authentication). It distinguishes from sibling tools like publish-blog, list-categories, list-tags which are unrelated.

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 usage before other operations by focusing on authentication, and provides instruction on obtaining the cookie from browser developer tools. However, it does not explicitly state when to use or when not to use, nor mention alternatives.

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