Skip to main content
Glama
ambit1977

Google Tag Manager MCP Server

by ambit1977

get_workspace

Retrieve detailed information about a specific workspace in Google Tag Manager by providing account, container, and workspace IDs.

Instructions

指定されたワークスペースの詳細を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesアカウントID
containerIdYesコンテナID
workspaceIdYesワークスペースID

Implementation Reference

  • Schema definition for the 'get_workspace' MCP tool, including input schema with accountId, containerId, and workspaceId.
    {
      name: 'get_workspace',
      description: '指定されたワークスペースの詳細を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          accountId: {
            type: 'string',
            description: 'アカウントID',
          },
          containerId: {
            type: 'string',
            description: 'コンテナID',
          },
          workspaceId: {
            type: 'string',
            description: 'ワークスペースID',
          },
        },
        required: ['accountId', 'containerId', 'workspaceId'],
      },
  • MCP tool handler for 'get_workspace' that extracts arguments, calls GTMClient.getWorkspace, and returns the result as formatted JSON text content.
    case 'get_workspace':
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              await this.gtmClient.getWorkspace(
                args.accountId,
                args.containerId,
                args.workspaceId
              ),
              null,
              2
            ),
          },
        ],
      };
  • Core implementation of getWorkspace that ensures authentication and calls the Google Tag Manager API to retrieve workspace details.
    async getWorkspace(accountId, containerId, workspaceId) {
      await this.ensureAuth();
      const response = await this.tagmanager.accounts.containers.workspaces.get({
        path: `accounts/${accountId}/containers/${containerId}/workspaces/${workspaceId}`
      });
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it retrieves details but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or what 'details' include. This is inadequate for a tool with no annotation coverage.

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, efficient sentence in Japanese that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded with the core action.

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

Completeness2/5

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

Given no annotations, no output schema, and a description that only states the basic purpose, this is incomplete. It lacks information on authentication, response format, error cases, and how it differs from sibling tools, which is insufficient for effective use.

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?

Schema description coverage is 100%, so the schema fully documents the three required parameters (accountId, containerId, workspaceId). The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high coverage.

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

Purpose4/5

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

The description clearly states the action ('取得します' - retrieve/get) and resource ('ワークスペースの詳細' - workspace details), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_container' or 'list_workspaces' beyond specifying it retrieves details for a specific workspace.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_workspaces' or 'get_container'. The description implies it's for retrieving details of a specific workspace but doesn't mention prerequisites (e.g., needing authentication) or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ambit1977/GTM-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server