Skip to main content
Glama

get_my_qiita_articles

Retrieve authenticated user's Qiita articles with pagination support using the MCP server tool, enabling access to articles based on page number and items per page.

Instructions

get current authenticated user qiita articles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
per_pageNoNumber of items per page

Implementation Reference

  • Main handler function that executes the tool logic: fetches paginated list of current user's Qiita articles via QiitaApiService, formats as JSON response or error.
    const getMyQiitaUserArticles = async (params: GetUserArticlesParams): Promise<any> => {
      try {
        const { page = 1, per_page = 20 } = params;
        const items = await apiService.getAuthenticatedUserItems(page, per_page);
        return createSuccessResponse(JSON.stringify(items, null, 2));
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return createErrorResponse(`Error fetching Qiita items: ${errorMessage}`);
      }
    };
  • Zod schema defining input parameters for the tool: optional page (default 1) and per_page (default 20).
    const getUserArticlesSchema = z.object({
      page: z.number().optional().default(1).describe("Page number for pagination"),
      per_page: z.number().optional().default(20).describe("Number of items per page"),
    });
  • Tool definition object within getToolDefinitions() array, specifying name, description, parameters, and handler reference.
    {
      name: "get_my_qiita_articles",
      description: "get current authenticated user qiita articles",
      parameters: getUserArticlesSchema.shape,
      handler: (params: GetUserArticlesParams) => getMyQiitaUserArticles(params)
    },
  • src/index.ts:19-21 (registration)
    MCP server registration loop that calls server.tool() for each tool definition from qiitaTools.ts.
    getToolDefinitions().forEach(({ name, description, parameters, handler }) => {
      server.tool(name, description, parameters, handler);
    });
  • QiitaApiService method implementing the core API call to fetch authenticated user's items, with token validation, error handling, and response filtering.
    getAuthenticatedUserItems = async (page: number = 1, per_page: number = 20): Promise<any[]> => {
      this.validateToken();
    
      const response = await fetch(
        `${this.baseUrl}/authenticated_user/items?page=${page}&per_page=${per_page}`, 
        { headers: this.getHeaders() }
      );
      
      if (!response.ok) {
        await this.handleErrorResponse(response);
      }
      
      const items = await response.json();
      return this.filterItems(items);
    };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's for getting articles, implying a read operation, but doesn't specify authentication requirements, rate limits, pagination behavior beyond the schema, or what the return format looks like. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness. No structural issues are present.

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 the tool's complexity (a read operation with pagination), lack of annotations, and no output schema, the description is incomplete. It doesn't explain authentication needs, return format, or error handling, leaving gaps for the agent. For a tool with 2 parameters and no structured behavioral hints, more context is needed to be fully helpful.

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?

The schema description coverage is 100%, with both parameters ('page' and 'per_page') well-documented in the schema itself. The description adds no additional meaning beyond what the schema provides, such as default values or usage context. Baseline 3 is appropriate when the schema does the heavy lifting, but no extra value is added.

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 verb ('get') and resource ('current authenticated user qiita articles'), making the purpose understandable. It distinguishes from siblings like 'get_qiita_item' by specifying it's for the authenticated user's articles, not general items. However, it doesn't explicitly contrast with 'post_qiita_article' or 'update_qiita_article', which are write operations, so it's not a perfect 5.

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 alternatives. It doesn't mention that 'get_qiita_item' might be for specific items by ID, or that 'post_qiita_article' and 'update_qiita_article' are for creating/modifying articles. There's no context on prerequisites like authentication, leaving the agent to infer usage from the name alone.

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

Related 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/2bo/qiita-mcp-server'

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