Skip to main content
Glama
Sign In

Brix Digital Signage

by com.brixsignage
OverviewDiscussionsAdmin

Sync data or re-render a web page

refresh_data
Idempotent

Pull fresh content now instead of at the next scheduled refresh.

When to use:

  • Before an announcement, so menus and prices are current; after someone edits a sheet that a creative repeats over; after changing a web link's crop with update_items, to see the result.

When NOT to use:

  • Changing a feed's or link's settings: use update_items. A screen that has not picked up a change, or is frozen: use control_screens.

What to know:

  • Settings never change. A failing feed is reported in the result, not thrown. Screens showing the data update when a sync succeeds. Needs integration.edit for feeds, media.edit for a web link.

  • A sheet published to the web changes on Google's side up to about 5 minutes after an edit, so a sync straight after an edit can still read the old rows: synced true says the sync ran, not that the edit arrived. Check rowCount with get_items and sync again after a few minutes if it is old.

Parameters:

  • Pass exactly one; none or two is an error.

  • dataSourceId: one ds_… feed from list_items kind data_sources.

  • allDataSources: true syncs every feed you can edit, one after another; one failure does not stop the rest; limited to 5 calls a minute.

  • webLinkId: one med_… web link (list_items kind media, mediaKind web); renders a new snapshot.

Input Schema

NameRequiredDescriptionDefault
webLinkIdNoWeb link id.
dataSourceIdNoData source id.
allDataSourcesNoEvery data source.

Output Schema

NameRequiredDescriptionDefault
okNoallDataSources: feeds that synced.
errorNoOne feed: why it did not sync.
totalNoallDataSources: feeds tried.
failedNoallDataSources: feeds that failed.
syncedNoOne feed: true when it synced.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / allDataSources / description
      Previous value: -"true syncs every data source you can edit."New value: +"Every data source."
    • changedInput schema / properties / dataSourceId / description
      Previous value: -"One data source id (ds_…), from list_items kind data_sources."New value: +"Data source id."
    • changedInput schema / properties / webLinkId / description
      Previous value: -"A web link media id (med_…), from list_items kind media with mediaKind web."New value: +"Web link id."
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by disclosing that settings never change, that failures surface in the result rather than as thrown errors, that permissions integration.edit / media.edit are required, and that allDataSources is throttled to 5 calls a minute. The Google-side propagation caveat (up to ~5 minutes; 'synced true' means the sync ran, not that the edit landed) is exactly the kind of trap an agent could not infer from structured fields.

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?

Front-loaded with the imperative sentence and cleanly sectioned into when/when-not/what-to-know/parameters, with no filler. The 'What to know' bullet is dense and multi-topic, packing permissions, failure mode, propagation delay, and verification advice into one block, which slightly hurts scannability even though almost every clause carries weight.

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

Completeness5/5

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

For a three-parameter, mutually exclusive, permission-gated tool this covers requirements, throttling, partial failure, and stale-read verification, and an output schema already documents return values. Nothing an agent needs to call it correctly or interpret the result is missing.

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

Parameters5/5

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

Although schema coverage is 100%, the schema only offers one-word descriptions ('Web link id.', 'Every data source.'). The description adds the decisive rule that exactly one of the three must be passed, gives ID prefixes (ds_…, med_…), and explains how to discover IDs via list_items kinds, plus the sequential and partial-failure semantics of allDataSources.

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 opening line states a specific verb and resource: pull fresh content now rather than at the next scheduled refresh, and the title clarifies it covers both data sync and web-link re-render. It is clearly separable from siblings that change settings (update_items) or manipulate screens (control_screens).

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

Usage Guidelines5/5

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

Explicit 'When to use' and 'When NOT to use' sections name the exact alternatives: update_items for settings changes and control_screens for a screen that is frozen or not picking up a change. The excluded cases are routed to a specific sibling rather than left to inference.

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

All Brix Digital Signage toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources