mcp-fabric-api

graphql_api_list

Read-only

List every GraphQL API item in a specified workspace, giving data engineers a complete view of Fabric API resources for effective management.

Instructions

List all GraphQL API items in a workspace

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>"
    },
    "name": "graphql_api_list"
  }
}

Input Schema

Name	Required	Description	Default
`workspaceId`	Yes	The workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare this as a safe read-only operation, so the description does not need to restate that. The description adds the workspace scoping context but does not disclose potential pagination, sorting, or volume-related behavior, which could matter for a 'list all' 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, focused sentence with no filler. It front-loads the action and resource, then specifies the scope. Every word earns its place.

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

Completeness4/5

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

For a one-parameter read-only list operation with complete schema coverage, the description is mostly sufficient. A small gap is the lack of any mention of return shape or pagination behavior, but the list verb strongly implies a collection response, and the annotations already cover the safety profile.

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?

The input schema has 100% coverage: the single required parameter workspaceId has a description. The tool description only repeats the workspace scope already present in the schema and adds no additional semantic detail about the parameter's format, constraints, or relationship to the listed items.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') with a clear resource ('GraphQL API items') and scope ('in a workspace'). This distinguishes it from sibling tools like graphql_api_get, which retrieves a single item, and graphql_api_execute_query, which runs operations.

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 for listing all GraphQL API items in a workspace, but it does not explicitly state when to use this tool versus alternatives such as graphql_api_get for a single item or graphql_api_get_definition for item details. No exclusions or routing guidance is provided.

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

Deploy Server