Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

get_uploads

Retrieve a list of uploads in a Basecamp project or specific vault by providing the project ID, enabling organized file management and tracking.

Instructions

List uploads in a project or vault

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
vault_idNoOptional vault ID to limit to specific vault

Implementation Reference

  • Core handler function in BasecampClient that retrieves uploads from a project or specific vault using the Basecamp API.
    async getUploads(projectId: string, vaultId?: string): Promise<Upload[]> {
      const endpoint = vaultId 
        ? `/buckets/${projectId}/vaults/${vaultId}/uploads.json`
        : `/buckets/${projectId}/uploads.json`;
      const response = await this.client.get(endpoint);
      return response.data;
    }
  • src/index.ts:461-472 (registration)
    Registers the 'get_uploads' tool in the MCP server's ListTools response, defining its name, description, and input schema. Note: No corresponding case handler in CallToolRequestSchema yet.
    {
      name: 'get_uploads',
      description: 'List uploads in a project or vault',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'Project ID' },
          vault_id: { type: 'string', description: 'Optional vault ID to limit to specific vault' },
        },
        required: ['project_id'],
      },
    },
  • Type definition for Upload objects returned by the getUploads handler.
    export interface Upload {
      id: string;
      filename: string;
      title?: string;
      description?: string;
      byte_size: number;
      content_type: string;
      created_at: string;
      creator: Person;
      download_url: string;
      project?: ProjectInfo;
    }
    
    export interface Webhook {
      id: string;
      payload_url: string;
      types: string[];
      created_at: string;
      updated_at: string;
    }
    
    export interface DailyCheckIn {
      id: string;
      title: string;
      created_at: string;
      updated_at: string;
      creator: Person;
    }
    
    export interface QuestionAnswer {
      id: string;
      content: string;
      created_at: string;
      creator: Person;
    }
    
    export interface SearchResults {
      projects?: BasecampProject[];
      todos?: Todo[];
      messages?: Message[];
      campfire_lines?: CampfireLine[];
      uploads?: Upload[];
    }
    
    export interface APIResponse<T = any> {
      status: 'success' | 'error';
      data?: T;
      error?: string;
      message?: string;
    }
    
    export interface MCPToolResult {
      status: 'success' | 'error';
      [key: string]: any;
    }
    
    export type AuthMode = 'basic' | 'oauth';
  • Interface defining the structure of upload data.
    export interface Upload {
      id: string;
      filename: string;
      title?: string;
      description?: string;
      byte_size: number;
      content_type: string;
      created_at: string;
      creator: Person;
      download_url: string;
      project?: ProjectInfo;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's a list operation. It doesn't disclose behavioral traits like pagination, sorting, filtering beyond project/vault, rate limits, authentication needs, or what the return format looks like (e.g., list of upload objects). This is inadequate for a tool with potential complexity.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what an 'upload' entails in this context, how results are returned, or any limitations. For a list tool with potential data volume and format considerations, this leaves significant gaps for the agent.

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?

Schema description coverage is 100%, so the schema already documents both parameters (project_id as required, vault_id as optional). The description adds minimal value by implying the parameters define the scope ('in a project or vault'), but doesn't provide additional semantics like format examples or constraints beyond what's in the 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?

The description clearly states the verb 'List' and the resource 'uploads', specifying the scope as 'in a project or vault'. However, it doesn't differentiate from potential sibling list tools like 'get_documents' or 'get_cards', which might have similar listing patterns but for different resources.

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 prerequisites, exclusions, or compare it to other list tools in the sibling set, leaving the agent to infer usage based on the resource 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/jhliberty/basecamp-mcp-server'

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