stitch-mcp-stdio

get_project

Read-only

Retrieve detailed information about a specific Stitch project by providing its project name. Use this to access project metadata and configuration.

Instructions

Retrieves the details of a specific Stitch project using its project name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Required. Identifier. The resource name of the project to retrieve. Format: `projects/{project}` Example: `projects/4044680601076201931`

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	Identifier. The resource name of the project. Format: projects/{project}
`title`	No	Optional. The title of the project.
`origin`	No	Output only. The origin of the project.
`metadata`	No	Metadata of the project.
`readTime`	No	Output only. The time the project was last read. Populated only when listing recently viewed projects.
`createTime`	No	Output only. The time when the project was created.
`deviceType`	No	Optional. The device type of the project.
`updateTime`	No	Output only. The time when the project was last updated.
`visibility`	No	Optional. The visibility setting of the project.
`designTheme`	No	Output only. The theme used to generate the first design in the project.
`projectType`	No	Optional. The type of the project. If not specified, the project is a text to UI project.
`backgroundTheme`	No	Optional. The background theme of the project.
`screenInstances`	No	Output only. The screen instances on this project.
`thumbnailScreenshot`	No	Optional. The screenshot to be used as the thumbnail for the project. Same as normal design screenshots, this contains the FIFE serving_base_url which requires additional FIFE URL options to be set for sizing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, and the description's 'Retrieves' is consistent with those. The description adds little behavioral context beyond that, such as failure behavior or scope, but the annotations lower the burden for this simple read operation.

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 sentence that states the action, target resource, and lookup key with no filler. The most important information is front-loaded and every word earns its place.

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

Completeness5/5

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

This is a low-complexity tool with one fully documented required parameter, an output schema, and read-only annotations. Nothing essential for correct invocation is missing.

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%, with the parameter's format and example fully documented as `projects/{project}`. The description only restates that the lookup uses the project name, adding no meaning beyond 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 uses a specific verb ('Retrieves') and a clear object ('details of a specific Stitch project'), so the core purpose is immediately understandable. It does not explicitly contrast with sibling tools, but 'specific project' distinguishes it from list_projects and other project mutations.

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 implies the tool is used when retrieving one project by name, but it gives no explicit when-to-use guidance or references to alternatives such as list_projects. An agent can infer basic usage, but exclusion criteria are absent.

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

Deploy Server