List Circuits In Experiment
List circuits that belong to an experiment.
Use this tool when the caller wants to inspect or choose circuits inside
one experiment before submitting runs, compression jobs, or follow-up job
lookups. Returned circuit.id values are valid inputs for execution,
compression, and circuit-job MCP tools.
When to Use:
- Call this when the caller already has an
experiment_idand needs candidate circuits for execution, compression, or further analysis. - Call this before
list_jobs_for_circuitwhen the relevant circuit has not yet been selected.
Constraints:
limitcontrols the maximum number of rows returned.- Circuit IDs returned here should be forwarded unchanged into later MCP calls.
Notes:
- Keep
limitreasonably small for model-facing workflows because circuit objects can include analytics and metadata. - For agent-facing output, summarize the count and top candidates before expanding full records.
Args:
experiment_id: Parent experiment identifier.
user: Authenticated user resolved from the API key.
db: Active database session.
circuit_ids (list[str] | None): When specified, filter out only specific circuits.
job_type (str | None): When specified, filter out only circuits that belong to specific job type.
Possible values are: “Analytics”, “Data Loading”, “Run”, “State Compression”,
“Transpilation”, “Variational”, “Pretraining”, “SKQD”.
limit: Maximum number of circuits to return. Defaults to 100.
Returns:
A list of circuit objects capped by limit.
Raises:
HTTPException: Raised with 404 when the experiment is not available
to the caller.
Authorizations
Path Parameters
Response
Successful Response
Class for circuit analytics calculation job status.
Submitted, Running analytics computation, Core metrics computation is done, Advanced metrics computation is done, Evolution computation is done, Done, Error Data model for circuit metrics.