bilt_get_project

Overview

Retrieves complete details for a single project by ID. Use this when you have a project ID and need its current state, metadata, or configuration.

You must own the project or have access to it. Private projects owned by others will return 403 Forbidden.

Parameters

string

required

Unique project identifier

Format: UUID
Example: "550e8400-e29b-41d4-a716-446655440000"
Get it from: bilt_list_projects or bilt_create_project

Response

string

required

Project identifier (same as input)

string

required

Project name

string

Project description (null if not set)

string

required

"public" or "private"

string

required

ISO 8601 timestamp of creation

string

required

ISO 8601 timestamp of last update

Example Usage

{
  "projectId": "550e8400-e29b-41d4-a716-446655440000"
}

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "name": "todo-app",
  "description": "A simple todo list application with authentication",
  "visibility": "public",
  "createdAt": "2026-02-10T10:30:00.000Z",
  "updatedAt": "2026-02-10T14:20:00.000Z"
}

Agent Workflow Examples

Pattern 1: Get Project Before Modifying

User: "Add a search feature to my todo app"

Agent workflow:
1. Call bilt_list_projects() to find "todo-app"
2. Call bilt_get_project(projectId) to confirm details
3. Call bilt_get_session() to start workflow
4. Call bilt_send_message("Add search feature")

Pattern 2: Check Project Status

User: "What's the status of my landing-page project?"

Agent workflow:
1. Call bilt_list_projects() to get project ID
2. Call bilt_get_project(projectId)
3. Check updatedAt to see when last modified
4. Report status to user

Pattern 3: Verify Ownership

Before performing operations:

Agent workflow:
1. Call bilt_get_project(projectId)
2. If successful → user owns project, proceed
3. If 403 error → user doesn't have access, inform them

Use Cases

Confirm project exists

Before starting work, verify the project is valid:

try {
  const project = await bilt_get_project({ projectId });
  console.log(`Working on: ${project.name}`);
} catch (error) {
  if (error.status === 404) {
    console.log("Project not found");
  }
}

Get project metadata

Retrieve name, description, visibility for display:

Agent: "Let me check that project..."

Result:
"Your project 'todo-app' is public and was last updated 
 on Feb 10 at 2:20 PM."

Check modification date

See when project was last changed:

const project = await bilt_get_project({ projectId });
const lastUpdate = new Date(project.updatedAt);
const hoursSince = (Date.now() - lastUpdate) / 3600000;

if (hoursSince > 24) {
  console.log("This project hasn't been touched in over a day");
}

Response Comparison

Success Response

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "name": "my-app",
  "description": "Description here",
  "visibility": "public",
  "createdAt": "2026-02-10T15:00:00.000Z",
  "updatedAt": "2026-02-10T15:30:00.000Z"
}

Project Not Found (404)

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32004,
    "message": "Resource not found"
  }
}

Access Denied (403)

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32003,
    "message": "Access denied - you do not have permission for this resource"
  }
}

Best Practices

Get before modifyAlways fetch project details before making changes

Handle 404s gracefullyUser may have deleted the project

Check updatedAtKnow when project was last touched

Use for validationConfirm project exists before long operations

Error Handling

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32602,
    "message": "Missing required parameter: projectId"
  }
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32001,
    "message": "Authentication failed - invalid or expired API key"
  }
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32003,
    "message": "Access denied - you do not have permission for this resource"
  }
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32004,
    "message": "Resource not found"
  }
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32005,
    "message": "Rate limit exceeded - please slow down requests"
  }
}

When to Use vs bilt_list_projects

Use bilt_get_project when
Use bilt_list_projects when

You have a project ID
Need detailed info on one project
Validating project exists
Checking specific project status

Performance

Response time: < 100ms typical
Payload size: ~400 bytes
Caching: Consider caching if accessed frequently

bilt_list_projects

Find project ID by name

bilt_create_project

Create new project

bilt_send_message

Start working on project

Next Steps

After getting project details:

Start a workflow - Use bilt_get_session
Send instructions - Use bilt_send_message
View history - Use bilt_get_messages

Get Started

Client Setup

Tools Reference

bilt_get_project

Overview

Parameters

Response

Example Usage

Agent Workflow Examples

Pattern 1: Get Project Before Modifying

Pattern 2: Check Project Status

Pattern 3: Verify Ownership

Use Cases

Response Comparison

Success Response

Project Not Found (404)

Access Denied (403)

Best Practices

Error Handling

When to Use vs bilt_list_projects

Performance

bilt_list_projects

bilt_create_project

bilt_send_message

Next Steps

​Overview

​Parameters

​Response

​Example Usage

​Agent Workflow Examples

​Pattern 1: Get Project Before Modifying

​Pattern 2: Check Project Status

​Pattern 3: Verify Ownership

​Use Cases

​Response Comparison

​Success Response

​Project Not Found (404)

​Access Denied (403)

​Best Practices

​Error Handling

​When to Use vs bilt_list_projects

​Performance

​Related Tools

bilt_list_projects

bilt_create_project

bilt_send_message

​Next Steps

Overview

Parameters

Response

Example Usage

Agent Workflow Examples

Pattern 1: Get Project Before Modifying

Pattern 2: Check Project Status

Pattern 3: Verify Ownership

Use Cases

Response Comparison

Success Response

Project Not Found (404)

Access Denied (403)

Best Practices

Error Handling

When to Use vs bilt_list_projects

Performance

Related Tools

Next Steps