Skip to main content
Glama

AutoTasker Hub — China Social Data API

juejin_hot

Juejin (掘金) recommended developer articles: title, brief, author, digg count. $0.01 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "juejin_hot"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the returned fields and the $0.01 USDC cost, which is genuinely useful before invocation, but it says nothing about read-only behavior, pagination, rate limits, or how payment is settled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A tight two-fragment description with no wasted words: resource and returned fields come first, cost follows. Slightly telegraphic, but appropriately sized for a simple feed tool.

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 simple read-only list with one optional parameter and no output schema, listing the returned fields is a reasonable substitute for an output schema. However, the omission of limit semantics and any hint about result ordering or freshness leaves clear 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 coverage is 0% and the single parameter (limit, default 10, maximum 20) is never mentioned in the description. The description therefore leaves the agent to discover the cap and default from the raw schema rather than compensating for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (Juejin recommended developer articles) and enumerates the returned fields (title, brief, author, digg count). It is distinguishable from the other *_hot siblings mainly by the named source, though it never explains how it differs from them beyond the platform.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all. Nothing tells the agent to pick this over baidu_hot, douyin_hot, or the other hot-list siblings, so selection is left entirely to inference from the source name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.