Skip to content

project_get

Managementcatalog

Get Project

Not in the default tool list

This tool lives in the tool catalog. Discover it with scenario_tools_search (or enumerate everything with scenario_tools_list) and run it via scenario_tool_execute_read. To list every tool directly, connect with ?toolsets=full.

Get one Scenario project: name, description, privacy mode, avatar asset id, settings, and credit consumption for the billing period (with its cap when one is set). Returns: { project, member_count, api_key_count }. Member and API-key rows are left out: use project_members_list / api_keys_list for those. Example: "What's in the Fantasy RPG project?" -> project_id="proj_xyz789", then assets_list or models_list with the same project_id. A project's contents are listed by the content tools with this project_id: assets_list, models_list, collections_list, workflows_list. Assets belong to exactly one project: asset_copy with target_project_id copies one into another project, model_transfer moves a model. Don't use when: you only need ids and names of every project in a team — use projects_list.
read-onlyidempotentopen-world

Parameters

NameTypeRequiredDescription
team_idstring—Team ID. Required with project_id for OAuth callers; an API key is scoped by the key.
project_idstring✓Project ID. Get it from projects_list.
response_formatenum(json | markdown)jsonOutput format: 'json' for structured data, 'markdown' for human-readable text.

Example Request

JSON
{
  "team_id": "team_abc123",
  "project_id": "proj_xyz789"
}

Example Response

JSON
{
  "project": {
    "id": "proj_xyz789",
    "teamId": "team_abc123",
    "name": "Fantasy RPG",
    "description": "Characters, props and key art for the RPG pitch.",
    "privacyMode": false,
    "consumption": 1840
  },
  "member_count": 4,
  "api_key_count": 1
}

Common Use Cases

  • Check the description, privacy mode and credit consumption of a project before working in it
  • See whether a project still has members or API keys before deleting it