Skip to main content
Glama
Sign In
MisarBlog MCP Server

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get reactions

get_reactions
Read-onlyIdempotent

Retrieves reaction counts and your reactions for a specific article by UUID, requiring an API key. Deprecated: use upvote_article or save_article for new work.

Instructions

Deprecated (the v1 reactions API sunsets on 2027-02-03): get reaction counts and your reactions for an article. Use upvote_article / save_article for new work. Requires API key.

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": {
      "article_id": "<article_id>"
    },
    "name": "get_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYesUUID of the article

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / article_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. Changed1 schema field changedv5.1.3
    • changedInput schema / properties / article_id / description
      Previous value: -"UUID of the article, from the `id` field returned by article tools."New value: +"UUID of the article"
  3. Changed1 schema field changedv5.1.0
    • changedInput schema / properties / article_id / description
      Previous value: -"UUID of the article"New value: +"UUID of the article, from the `id` field returned by article tools."
  4. First observedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely new context: the deprecation lifecycle, the sunset date, and the API-key auth requirement. It stops short of describing the response shape, but with no output schema that is a minor gap for a simple read.

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?

One sentence, front-loaded with the deprecation warning, followed by the functional statement, the migration path, and the auth note. No wasted wording.

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 one-parameter read tool with full annotation coverage and full schema coverage, the description supplies everything an agent needs: what it returns conceptually, that it is deprecated, when it sunsets, what to use instead, and that an API key is required.

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?

There is a single parameter (article_id) with 100% schema description coverage including UUID format and pattern, so the schema fully documents it. The description adds no parameter-level meaning beyond that, which is the expected baseline when schema coverage is complete.

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?

States a specific verb and resource: 'get reaction counts and your reactions for an article.' The scope ('counts' plus 'your reactions') is precise enough to distinguish it from the mutation siblings add_reaction/remove_reaction/upvote_article.

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?

Explicitly flags the tool as deprecated with a concrete sunset date (2027-02-03) and names the replacement tools (upvote_article / save_article) for new work. This is exactly the when-not-to-use and alternative routing an agent needs.

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