Skip to main content
Glama

plurk_get_thread_context

Retrieve parent plurk and normalized replies for a specific thread using provided credentials to access conversation context.

Instructions

Return the parent plurk and normalized replies for a specific thread using the supplied credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
credentialsYes
plurkIdYes

Implementation Reference

  • The implementation of the getThreadContext service method.
    public async getThreadContext(
      adapterSource: AdapterSource,
      credentials: PlurkCredentialsInput,
      plurkId: number,
    ): Promise<ThreadContext> {
      if (!Number.isInteger(plurkId) || plurkId <= 0) {
        throw new ServiceError("validation", "plurkId must be a positive integer", {
          metadata: { plurkId },
        });
      }
    
      return this.runReadAction(
        "get-thread-context",
        adapterSource,
        credentials,
        async (context) =>
          context.client.getThreadContext(plurkId, context.profile.nickName ?? ""),
      );
    }
  • Registration of the plurk_get_thread_context tool.
    {
      name: "plurk_get_thread_context",
      description:
        "Return the parent plurk and normalized replies for a specific thread using the supplied credentials.",
      inputSchema: z.object({
        credentials: credentialsSchema,
        plurkId: z.number().int().positive(),
      }),
      execute: async ({ credentials, plurkId }) =>
        application.getThreadContext("mcp", credentials, plurkId),
Behavior3/5

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

Discloses 'normalized replies' processing behavior and implies credential-based auth. However, lacks details on what 'normalized' means, response structure, rate limits, or pagination given zero annotations provided.

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?

Single sentence, front-loaded with action verb. Every phrase earns its place: 'normalized' signals processing, 'parent plurk' distinguishes from replies, 'supplied credentials' establishes auth requirement.

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?

Adequate basic description but insufficient given complexity: nested credential object with 4 undocumented fields, no output schema, and no annotations. Missing crucial details like what constitutes a valid plurkId or expected response format.

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?

With 0% schema coverage, description compensates partially: 'supplied credentials' maps to auth object and 'specific thread' implies plurkId identifies the thread. However, fails to document the 4 required credential sub-fields (appKey, appSecret, etc.) or plurkId value format.

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?

Specific verb 'Return' with clear resource 'parent plurk and normalized replies' and scope 'specific thread'. Distinct from siblings: plurk_post/reply are write operations, plurk_get_alerts/mentions_context retrieve different data types.

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?

No guidance on when to use this vs plurk_get_mentions_context or other retrieval tools. No mention of prerequisites like needing a valid plurkId from a previous search.

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