Skip to main content
Glama

Get Reverse Etl Process Tool

get-reverse-etl-process
Read-onlyIdempotent

Return the full configuration, SQL, schedule, and delivery settings for one reverse ETL process. Requires data-distribution permission. process_id is a string. destination matches the destination type: custom HTTP fields, Telegram settings, or the Google Ads conversions URL. preset_config is the Telegram text mode or Google Ads builder config, or null.

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": {
      "process_id": "<process_id>"
    },
    "name": "get-reverse-etl-process"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoSpace slug. Required when the token is bound to more than one space. Omit it when the token has one space.
process_idYesReverse ETL process id.

Output Schema

NameRequiredDescriptionDefault
nameYes
statusYes
process_idYes
project_idYes
destinationNoShape depends on preset_type: null (custom HTTPS), telegram, or google_ads.
project_nameNo
data_settingsYes
preset_configNoPresent only for the destination preset. Null for custom destinations, unset Telegram text mode, and manual Google Ads SQL.
destination_idYes
destination_nameNo
delivery_settingsYes
permission_noticeYes
execution_settingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds genuinely new context: a required data-distribution permission, which is operationally important before an agent attempts the call. It does not disclose failure behavior for a missing or inaccessible process_id, keeping it below a 5.

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

Conciseness3/5

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

The purpose is front-loaded in the first sentence, but the trailing sentences about destination, preset_config and destination types are not clearly framed as return-value fields and read as if they were parameters. Roughly half the text addresses information an output schema already carries.

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

Completeness3/5

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

An output schema exists, so return-value detail is not strictly required, and the description does cover purpose and permissions. However, it omits guidance on the space parameter's multi-space condition beyond what the schema states, and its unlabeled field discussion leaves the agent unsure whether destination/preset_config are inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description does not improve on it. It restates that process_id is a string (already in the schema) and then discusses 'destination' and 'preset_config', which are not input parameters at all, creating ambiguity about whether they should be supplied.

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?

States a specific verb and resource ('Return the full configuration, SQL, schedule, and delivery settings for one reverse ETL process') and the singular scope implicitly distinguishes it from list-reverse-etl-processes. It stops short of naming the sibling alternative or stating the relationship explicitly, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the detail-fetch counterpart to the list tool. There is no explicit when-to-use/when-not guidance and no mention of what to do if the process_id is unknown or which sibling to call first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources