Skip to main content
Glama

plurk_get_mentions_context

Retrieve recent mentions and conversation context from Plurk to plan replies or create summaries using authenticated credentials.

Instructions

Return recent mention-driven interactions and context suitable for summarization or reply planning for the supplied credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
credentialsYes
limitNo

Implementation Reference

  • The implementation of the getMentionsContext method in the PlurkApplication service, which executes the business logic for fetching mention-driven interactions.
    public async getMentionsContext(
      adapterSource: AdapterSource,
      credentials: PlurkCredentialsInput,
      limit = 20,
    ): Promise<MentionContext[]> {
      return this.runReadAction(
        "get-mentions-context",
        adapterSource,
        credentials,
        async (context) =>
          context.client.getMentionsContext(context.profile.nickName ?? "", limit),
      );
    }
  • The registration of the 'plurk_get_mentions_context' tool in the MCP tool catalog, mapping it to the application service call.
      name: "plurk_get_mentions_context",
      description:
        "Return recent mention-driven interactions and context suitable for summarization or reply planning for the supplied credentials.",
      inputSchema: z.object({
        credentials: credentialsSchema,
        limit: positiveLimitSchema,
      }),
      execute: async ({ credentials, limit }) =>
        application.getMentionsContext("mcp", credentials, limit),
    },
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden. It mentions 'recent' and 'interactions' but fails to state whether this is read-only (implied only by 'Return'), what 'recent' means temporally, rate limits, or what the return format contains.

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

Conciseness3/5

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

Single sentence with reasonable density. 'Suitable for summarization or reply planning' adds value, though 'for the supplied credentials' is somewhat redundant with the required schema parameter. Adequately front-loaded but not exceptional.

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

Completeness2/5

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

Given zero annotations, no output schema, and 0% parameter documentation, the description should work harder to explain parameter semantics, differentiate from siblings (get_alerts vs. mentions), and disclose behavioral traits. It covers basic purpose but leaves critical gaps unfilled.

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 has 0% description coverage, yet the description only mentions 'credentials' in passing without explaining the OAuth structure (4 nested fields) or the 'limit' parameter (default 20, max 100). Insufficient compensation for the undocumented schema.

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?

Clear verb ('Return') and resource ('mention-driven interactions and context'). Specifies the domain (mentions vs. general alerts or threads), though it could more explicitly contrast with siblings like plurk_get_alerts or plurk_get_thread_context.

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?

Provides implied usage via 'suitable for summarization or reply planning,' giving the agent a hint about when to invoke it. However, lacks explicit when-not-to-use guidance or named alternatives (e.g., 'use plurk_get_thread_context instead for specific conversation threads').

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/congcongfu/plurk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server