Skip to main content
Glama
MustafaPatharia

ProofHub MCP Server

proofhub_get_task

Fetch task details (title, description, stage, custom fields, assignees) from ProofHub by specifying project, list, and task IDs.

Instructions

Fetch full task details (title, description, stage, custom fields, assignees) from ProofHub.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
list_idYes
task_idYes

Implementation Reference

  • Handler function for the 'proofhub_get_task' tool. Extracts project_id, list_id, task_id from args, calls apiGet to fetch the task from the ProofHub API, and returns the task data as JSON.
    // ── proofhub_get_task ────────────────────────────────────────────────
    if (name === 'proofhub_get_task') {
      const { project_id, list_id, task_id } = args;
      const task = await apiGet(`/projects/${project_id}/todolists/${list_id}/tasks/${task_id}`);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(task, null, 2),
        }],
      };
    }
  • Schema/registration input definition for 'proofhub_get_task'. Declares the tool name, description, and input schema with required fields project_id, list_id, task_id.
    {
      name: 'proofhub_get_task',
      description: 'Fetch full task details (title, description, stage, custom fields, assignees) from ProofHub.',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string' },
          list_id:    { type: 'string' },
          task_id:    { type: 'string' },
        },
        required: ['project_id', 'list_id', 'task_id'],
      },
    },
  • index.js:102-187 (registration)
    Tool registration via ListToolsRequestSchema handler. The object at lines 117-129 defines proofhub_get_task within the list of all tools that get registered with the MCP server.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: 'proofhub_parse_url',
          description:
            'Parse a ProofHub task URL and return the project ID, list ID, and task ID embedded in it. ' +
            'Use this as the first step before calling other ProofHub tools.',
          inputSchema: {
            type: 'object',
            properties: {
              url: { type: 'string', description: 'Full ProofHub task URL, e.g. https://kpi.proofhub.com/bappswift/#app/todos/project-7189443252/list-270280503800/task-514774338823' },
            },
            required: ['url'],
          },
        },
        {
          name: 'proofhub_get_task',
          description: 'Fetch full task details (title, description, stage, custom fields, assignees) from ProofHub.',
          inputSchema: {
            type: 'object',
            properties: {
              project_id: { type: 'string' },
              list_id:    { type: 'string' },
              task_id:    { type: 'string' },
            },
            required: ['project_id', 'list_id', 'task_id'],
          },
        },
        {
          name: 'proofhub_get_comments',
          description: 'Fetch all comments on a ProofHub task, including their full text.',
          inputSchema: {
            type: 'object',
            properties: {
              project_id: { type: 'string' },
              list_id:    { type: 'string' },
              task_id:    { type: 'string' },
            },
            required: ['project_id', 'list_id', 'task_id'],
          },
        },
        {
          name: 'proofhub_get_task_with_bug_links',
          description:
            'One-shot tool: given a ProofHub task URL (or IDs), fetches the task description AND all comments, ' +
            'then extracts any bug-tracker links (Jira, Linear, GitHub Issues, GitLab, YouTrack, ClickUp, Asana, etc.) ' +
            'found in any of those texts. Returns the task data plus a deduplicated list of bug links.',
          inputSchema: {
            type: 'object',
            properties: {
              url:        { type: 'string', description: 'Full ProofHub task URL (preferred). If supplied, project_id/list_id/task_id are ignored.' },
              project_id: { type: 'string' },
              list_id:    { type: 'string' },
              task_id:    { type: 'string' },
            },
          },
        },
        {
          name: 'proofhub_create_comment',
          description: 'Post a new comment on a ProofHub task.',
          inputSchema: {
            type: 'object',
            properties: {
              project_id:  { type: 'string' },
              list_id:     { type: 'string' },
              task_id:     { type: 'string' },
              description: { type: 'string', description: 'Comment text (plain text or HTML).' },
            },
            required: ['project_id', 'list_id', 'task_id', 'description'],
          },
        },
        {
          name: 'proofhub_get_task_history',
          description: 'Fetch the activity history of a ProofHub task (stage changes, edits, etc.).',
          inputSchema: {
            type: 'object',
            properties: {
              project_id: { type: 'string' },
              list_id:    { type: 'string' },
              task_id:    { type: 'string' },
            },
            required: ['project_id', 'list_id', 'task_id'],
          },
        },
      ],
    }));
  • Helper function apiGet used by the handler to make authenticated GET requests to the ProofHub API with automatic retry on 429 rate-limit responses.
    async function apiGet(url) {
      try {
        const res = await http.get(url);
        return res.data;
      } catch (err) {
        if (err.response?.status === 429) {
          const retryAfter = parseInt(err.response.headers['retry-after'] || '5', 10);
          await new Promise(r => setTimeout(r, retryAfter * 1000));
          return apiGet(url);
        }
        throw new Error(`ProofHub API error ${err.response?.status}: ${JSON.stringify(err.response?.data) || err.message}`);
      }
    }
Behavior2/5

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

No annotations provided. The description only implies a read operation ('Fetch') but does not disclose any additional behaviors such as authentication requirements, rate limits, or side effects.

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 sentence, clear and to the point. No unnecessary words. Could be slightly improved by structuring or providing a brief example.

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?

No output schema, no parameter descriptions, and no annotations. The description lists fields returned but lacks enough context for an AI to confidently use this tool, especially given three required IDs with no explanations.

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%, so the description should compensate. However, it only lists parameters by name and provides no extra meaning (e.g., how to obtain project_id, list_id, task_id).

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?

Clearly states the verb 'Fetch' and resource 'full task details', listing specific fields (title, description, stage, custom fields, assignees). Distinguishes from sibling tools like 'get_task_history' and 'get_task_with_bug_links'.

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 tool versus alternatives such as 'proofhub_get_task_with_bug_links' or 'proofhub_get_comments'. Does not specify prerequisites or when not to use.

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/MustafaPatharia/proofhub-mcp'

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