Skip to main content
Glama
wtznicy

MyWebSearch

by wtznicy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fetchJuejinArticle

Read-onlyIdempotent

Fetch full article text from a Juejin post URL. Use markdown output to keep code blocks and tables, making technical posts readable.

Instructions

Fetch full article content from a Juejin(掘金) post URL (juejin.cn or article.juejin.cn /post/ only; for other sites use fetchWebContent)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
formatNoOutput format (default: text). 'markdown' keeps fenced code blocks (with language) and GFM tables — recommended for technical posts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.17
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Output format (default: text). 'markdown' keeps fenced code blocks (with language) and GFM tables — recommended for technical posts",
+  "enum": [
+    "text",
+    "markdown"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.11

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds extra behavioral context by constraining the accepted URL to Juejin post URLs only, which is useful beyond the annotations.

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, front-loaded sentence that states the purpose, scope, and primary alternative with zero filler. Every word earns its place.

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

Completeness5/5

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

For a simple read-only fetch tool with 2 parameters and no output schema, the description plus schema provides all needed context: what tool does, what URLs to pass, and what format options exist. Annotations cover side effects, so nothing essential is missing.

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 only 50% (url has no schema description), but the description compensates by specifying the allowed domains and path for the url parameter. The format parameter is already documented in the schema with enum and description, so the description's added value for semantics is solid.

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 clearly states the specific verb/resource: 'Fetch full article content from a Juejin post URL'. It also specifies the exact URL pattern (juejin.cn or article.juejin.cn /post/ only) and names a sibling alternative (fetchWebContent), making it distinguishable from other fetch tools.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance ('from a Juejin post URL') and when-not-to-use guidance ('for other sites use fetchWebContent'), directly routing agents to the correct alternative. This is clear and actionable.

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