Skip to main content
Glama

get_project

Retrieve project details including page counts, scrape, rewrite, and publish progress for a given project ID.

Instructions

Get project details including stats (page counts, scrape/rewrite/publish progress)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject UUID

Implementation Reference

  • The tool handler for 'get_project'. It receives project_id, calls client.getProject(), and returns the project data as JSON.
    withErrors(async ({ project_id }) => {
      const res = await client.getProject(project_id);
      return json(res.data);
    })
  • src/tools.ts:89-100 (registration)
    Registration of the 'get_project' tool with description, UUID schema validation, metadata flags (readOnly, idempotent, openWorld), and handler binding.
    server.tool(
      "get_project",
      "Get project details including page-count stats and scrape/rewrite/publish progress.",
      {
        project_id: z.string().uuid().describe("Project UUID"),
      },
      { title: "Get project", readOnlyHint: true, idempotentHint: true, openWorldHint: true },
      withErrors(async ({ project_id }) => {
        const res = await client.getProject(project_id);
        return json(res.data);
      })
    );
  • Zod schema defining the input parameter: project_id (UUID string).
    {
      project_id: z.string().uuid().describe("Project UUID"),
  • The HTTP client method getProject() that sends a GET request to /api/v1/projects/{id} and returns ApiResponse<ProjectData>.
    async getProject(id: string): Promise<ApiResponse<ProjectData>> {
      return this.request("GET", `/api/v1/projects/${id}`);
    }
  • The ProjectData interface defining the shape of the response data (project_id, domain, name, job_id, page_count, stats, created_at).
    export interface ProjectData {
      project_id: string;
      domain: string;
      name: string;
      job_id?: string;
      page_count?: number;
      stats?: Record<string, unknown>;
      created_at?: string;
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses read-only nature and returned stats, but lacks details on potential errors, permissions, or response format.

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?

Single sentence, front-loaded with verb and resource, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple read tool with one parameter, but lacks usage guidance and behavior details that would improve completeness given sibling tools and no output schema.

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 covers 100% of parameters with 'Project UUID' description. Description adds no extra meaning for the parameter beyond the schema.

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?

The description clearly states the tool retrieves project details with specific stats like page counts and progress, distinguishing it from siblings like get_page or get_project_overview.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives (e.g., get_project_overview). Usage is implied but not clarified.

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

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/web-resurrect/mcp'

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