Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Channel Playstore Service Account

channel_playstore_service_account
Idempotent

Creates or retrieves your organization's Google Play service account for review replies; invite its email in Play Console before creating a PLAYSTORE channel.

Instructions

The Google service account of the organization for Google Play reviews (created on the first call). The user invites its email in the Play Console (Users and permissions, with the permission to reply to reviews) before channel_create with type PLAYSTORE works.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "channel_playstore_service_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

The phrase "created on the first call" explains why readOnlyHint is false despite the tool reading like a getter, and it signals idempotent lazy initialization, which annotations alone only hint at. It also discloses an out-of-band human dependency (Play Console invitation) that no annotation captures. It stops short of stating the exact response shape or failure behavior before the invite occurs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, no filler, and the creation-on-first-call fact is front-loaded before the prerequisite workflow. Slightly dense/run-on phrasing in the second sentence, but every clause carries information.

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 tool with full schema coverage and no output schema, the description covers the key unknowns: lazy creation on first call and the required Play Console invitation enabling channel_create PLAYSTORE. Only the returned field(s) are left implicit (the email is implied by "its email").

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?

With a single parameter and 100% schema description coverage that already says to use organization_list to find the id, the schema does the work. The description adds no extra meaning about the organizationId beyond what is already documented, so the baseline of 3 applies.

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 names the specific resource (the organization's Google service account used for Google Play reviews) and ties it to a concrete downstream action (invite the email, then channel_create with type PLAYSTORE). The verb is left implicit in a noun phrase ("The Google service account of the organization"), so an agent must infer it is a retrieval/creation-on-demand call, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It lays out the workflow: get this, invite the email in Play Console with reply-to-reviews permission, then channel_create with type PLAYSTORE will work. That effectively tells the agent when to call it. There is no explicit exclusion of alternatives (e.g. channel_get or channel_connect), but the sequencing guidance is clear.

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

Deploy Server

Other Tools