Skip to main content
Glama

get_project_assets

Retrieve assets for a WebSim project version to access project resources and content.

Instructions

Get assets for a specific project version

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesWebSim project ID
versionNoProject version (default: latest)latest

Implementation Reference

  • The MCP tool handler for 'get_project_assets' that validates input with ProjectRevisionSchema, fetches assets via apiClient, and formats the response as JSON text content.
    handler: async (args) => {
      const { project_id, version = 'latest' } = ProjectRevisionSchema.parse(args);
      const result = await apiClient.getProjectAssets(project_id, version);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            data: result,
            message: `Successfully retrieved assets for project ${project_id} (version: ${version})`
          }, null, 2)
        }]
      };
    }
  • Input schema defining the parameters for the 'get_project_assets' tool: project_id (required string) and version (optional string, default 'latest').
    inputSchema: {
      type: "object",
      properties: {
        project_id: {
          type: "string",
          description: "WebSim project ID"
        },
        version: {
          type: "string",
          description: "Project version (default: latest)",
          default: "latest"
        }
      },
      required: ["project_id"]
    },
  • server.js:966-998 (registration)
    The tool registration object added to the 'tools' array, specifying name, description, inputSchema, and handler for 'get_project_assets'.
    {
      name: "get_project_assets",
      description: "Get assets for a specific project version",
      inputSchema: {
        type: "object",
        properties: {
          project_id: {
            type: "string",
            description: "WebSim project ID"
          },
          version: {
            type: "string",
            description: "Project version (default: latest)",
            default: "latest"
          }
        },
        required: ["project_id"]
      },
      handler: async (args) => {
        const { project_id, version = 'latest' } = ProjectRevisionSchema.parse(args);
        const result = await apiClient.getProjectAssets(project_id, version);
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              success: true,
              data: result,
              message: `Successfully retrieved assets for project ${project_id} (version: ${version})`
            }, null, 2)
          }]
        };
      }
    },
  • Helper method in WebSimAPIClient class that makes the HTTP request to retrieve assets for a specific project revision/version.
    async getProjectAssets(projectId, version = 'latest') {
      const params = new URLSearchParams({ version });
      return this.makeRequest(`/api/v1/projects/${projectId}/revisions/${version}/assets?${params}`);
    }
  • Zod validation schema used by the tool handler to parse and validate the input arguments (project_id required, version optional).
    const ProjectRevisionSchema = z.object({
      project_id: z.string().describe('WebSim project ID'),
      version: z.string().optional().describe('Project version (default: latest)')
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states a read operation ('Get') but does not mention permissions, rate limits, pagination, error handling, or what the return format looks like. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 lack of annotations and no output schema, the description is incomplete. It does not explain what 'assets' entail, the return structure, or any behavioral aspects like safety or performance. For a tool with no structured support, the description should provide more context 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 input schema has 100% description coverage, with clear documentation for both parameters (project_id and version). The description adds no additional semantic details beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 the resource 'assets for a specific project version', which is specific and actionable. However, it does not distinguish this tool from sibling tools like 'search_assets' or 'search_relevant_assets', which might also retrieve assets, so it lacks sibling differentiation.

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 like 'search_assets' or 'list_all_projects'. It implies usage for a specific project version but offers no exclusions, prerequisites, or explicit comparisons to other tools.

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/gigachadtrey/websimm'

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