> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get project

> Read one project available to this credential.

`get_project`

Read one project available to this credential.

<Note>Development preview. This command is absent from the hosted MCP readback. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL\_API\_URL; production does not expose these command routes.</Note>

| Access          | Behavior         |
| --------------- | ---------------- |
| `projects:read` | Reads saved data |

Reading saved data does not start a verification job. Mutations can change saved records or access; the effects below apply.

## Example request

Connect through [MCP](/guides/connect-mcp), [CLI](/guides/connect-cli), or [HTTP](/guides/connect-http). Replace example identifiers with records from your workspace.

<CodeGroup>
  ```json MCP theme={null}
  {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "get_project",
      "arguments": {
        "projectId": "project_example"
      }
    }
  }
  ```

  ```bash CLI theme={null}
  linktrail call get_project --args '{"projectId":"project_example"}'
  ```

  ```bash HTTP theme={null}
  curl "$LINKTRAIL_API_URL/v1/commands/get_project" \
    -H "Authorization: Bearer $LINKTRAIL_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{"projectId":"project_example"}'
  ```
</CodeGroup>

## Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in `structuredContent` and in a text content block; generic HTTP and CLI return the JSON result directly.

```json theme={null}
{
  "id": "project_example",
  "workspace_id": "ws_example",
  "name": "Example project",
  "domain": "example.com",
  "created_at": "2026-09-13T12:00:00.000Z"
}
```

## Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

| Field       | Type   | Presence | Meaning and constraints                                                                          |
| ----------- | ------ | -------- | ------------------------------------------------------------------------------------------------ |
| `projectId` | string | Required | Identifier of the project returned by its create or list operation. minLength: 1; maxLength: 200 |

### Validation and omitted values

This operation has no omitted-input defaults. Supply its required identifiers from an accessible saved record.

## Output fields

Fields inside optional or nullable parents apply only when that parent exists. [Common schema conventions](/reference/schemas) explain evidence states, empty lists and extensions.

| Field          | Type    | Presence | Meaning and constraints                                                              |
| -------------- | ------- | -------- | ------------------------------------------------------------------------------------ |
| `id`           | string  | Required | Resource identifier returned by the operation.                                       |
| `workspace_id` | string  | Required | Workspace that owns this record.                                                     |
| `name`         | string  | Required | name recorded for this result.                                                       |
| `domain`       | string  | Required | domain recorded for this result.                                                     |
| `created_at`   | string  | Required | UTC timestamp when the record was created.                                           |
| `created`      | boolean | Optional | True when this request created the record; false when an existing record was reused. |

[Download input schema](/schemas/get_project.input.json) · [Download output schema](/schemas/get_project.output.json)

## Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. Operation-specific errors include `UNAUTHORIZED`, `INSUFFICIENT_SCOPE`, `WORKSPACE_ACCESS_DENIED`, `INVALID_GRANT`, `INVALID_INPUT`, `PROJECT_NOT_FOUND`.

See [error recovery](/reference/errors) for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

## HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See [HTTP route details](/reference/http/routes).

| Method and route               | Success | Details                                          |
| ------------------------------ | ------- | ------------------------------------------------ |
| `GET /v1/projects/{projectId}` | 200     | Remaining read arguments go in query parameters. |

## Continue

[list\_link\_watches](/reference/commands/list_link_watches) · [list\_discovery\_runs](/reference/commands/list_discovery_runs)

Follow the [related workflow](/guides/connect-http), inspect [capability status](/capability-status), or return to the [command index](/reference/index).