Skip to main content
Glama
Sign In
MisarBlog MCP Server

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List my articles

list_my_articles
Read-onlyIdempotent

Retrieve and filter your Misar.Blog articles by status or limit to review drafts, published, scheduled, or archived posts.

Instructions

List your articles on Misar.Blog

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": "list_my_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of articles to return
statusNoFilter by status (omit for all published)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv5.1.3
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum articles to return, 1-100. Defaults to 20."New value: +"Number of articles to return"
    • changedInput schema / properties / status / description
      Previous value: -"Return only articles in this state. Omit to return every state the account owns."New value: +"Filter by status (omit for all published)"
  3. Changed2 schema fields changedv5.1.0
    • changedInput schema / properties / limit / description
      Previous value: -"Number of articles to return"New value: +"Maximum articles to return, 1-100. Defaults to 20."
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status (omit for all published)"New value: +"Return only articles in this state. Omit to return every state the account owns."
  4. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered upstream. The description adds nothing behavioral beyond that — notably it omits the default behavior implied by the schema (omitting status returns published articles only), which is a meaningful quirk an agent should know before calling.

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?

A single six-word sentence with the resource and scope front-loaded and zero filler. Nothing in it is redundant or wasted.

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 listing tool with complete schema documentation and rich annotations, the minimal description is close to sufficient. However, it omits the default-status behavior and how to page through results beyond the limit cap, both of which affect correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, with both limit and status fully documented including enum values and the default. The description adds no additional parameter meaning, so the baseline of 3 applies where the schema does all the work.

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?

The description names a specific verb ("List") and resource ("articles") with an ownership scope ("your"), scoped to the Misar.Blog platform. It is clear what the tool returns, but it does not distinguish it from sibling tools like search_articles or list_saved, which an agent must infer on its own.

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. The description never says how this differs from search_articles when the agent wants to find articles by criteria, nor does it mention any prerequisite such as being logged in.

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