plurk-mcp

plurk_get_me

Retrieve the authenticated Plurk user profile using provided API credentials to access account information and context.

Instructions

Return the authenticated Plurk account profile for the credentials supplied in this call.

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": {
      "credentials": "<credentials>"
    },
    "name": "plurk_get_me"
  }
}

Input Schema

Name	Required	Description	Default
`credentials`	Yes

Implementation Reference

src/services/plurkApplication.ts:106-113 (handler)

The `getMe` method in `PlurkApplication` retrieves the profile from the pre-resolved `context.profile` within a read action wrapper that handles audit logging.

public async getMe(
  adapterSource: AdapterSource,
  credentials: PlurkCredentialsInput,
): Promise<ProfileData> {
  return this.runReadAction("get-me", adapterSource, credentials, async (context) => {
    return context.profile;
  });
}

src/transports/mcp/toolCatalog.ts:27-32 (registration)

Registration of the `plurk_get_me` tool in the `buildToolCatalog` function.

{
  name: "plurk_get_me",
  description: "Return the authenticated Plurk account profile for the credentials supplied in this call.",
  inputSchema: z.object({ credentials: credentialsSchema }),
  execute: async ({ credentials }) => application.getMe("mcp", credentials),
},

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 2, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full disclosure burden. While 'Return' implies a read-only operation, the description fails to disclose error behaviors (invalid credentials), rate limits, or what profile fields are returned. It mentions 'credentials supplied' but doesn't clarify these are OAuth 1.0a tokens requiring specific procurement steps.

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?

Single efficient sentence that front-loads the action ('Return') and resource ('authenticated Plurk account profile'). No redundant phrases, though extreme brevity contributes to informational gaps.

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 schema descriptions, no output schema, complex nested authentication requirements, and presence of sibling tools, the description is incomplete. It should explain the OAuth credential structure, indicate what profile data is returned, and clarify error conditions for invalid authentication.

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 description coverage is 0% for the four nested credential fields (appKey, appSecret, accessToken, accessTokenSecret). The description mentions 'credentials supplied' which maps to the parameter name, but provides no semantic explanation for the OAuth credential components, their format, or how to obtain them, leaving the complex nested object effectively undocumented.

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 clearly states the tool 'Return[s] the authenticated Plurk account profile' with specific resource (account profile) and action (Return/Retrieve). It implicitly distinguishes from siblings (get_alerts, get_thread_context, post, reply) by specifying this retrieves the user's own profile rather than content or alerts.

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?

The description provides no guidance on when to use this tool versus siblings (e.g., when needing user ID or display name versus getting mentions), nor does it mention prerequisites like required OAuth permissions or token validity checks.

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

Deploy Server