Skip to main content
Glama

put_pvr_programmed_id

Update properties of a scheduled recording on your Freebox, including start/end times, channel, name, and enable state. Handles errors like conflicts or disk full.

Instructions

Update a Precord properties

Error codes: noent, inval, inval_date_fmt, inval_end_before_start, system_time_incorrect, record_duration_too_long, record_date_in_past, unknown_channel, no_channel_svc, only_auto_disable, cannot_change_en_state, cannot_disable_has_data, internal_error, none, file_access_error, disk_full, private_but_no_private_dir, network_problem, resource_problem, no_stream_available, no_data_received, missed, stopped, unknown_error

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id__pathYes(Path parameter)
idNoprecord id
mediaNomedia name on which the record will be written to. See the Media API for more info. This property and can be empty when the file backing the record is not available, for example when secure is set.
pathNodestination directory on the media storage where the record will be written to
has_record_genNoif true, this precord has been generated using a Generator
record_gen_idNoif has_record_gen, this is the id of the generator
conflictNoif true this record may conflict with another record
overlap_listNoin case of conflict, this will contain the list of records id that may conflict with this record
enabledNoit only applies to generated records. If false the generated precord will be skipped.
alteredNoa precord is altered when some part of the recording may be missing. This can be the case if a conflict occurred during the recording (or connection was down)
stateNoValues: `disabled`: disabled; `start_error`: failed to start; `waiting_start_time`: scheduled; `starting`: starting; `running`: running; `running_error`: running with error; `failed`: failed; `finished`: finished
errorNo
channel_uuidNochannel uuid
channel_nameNooptional channel name
channel_qualityNo
channel_typeNoValues: `‘’ (empty string)`: auto; `iptv`: use only iptv streams; `dvb`: use only dvb streams
nameNorecord name
subnameNorecord subname
broadcast_typeNo
startNorecord start timestamp
endNorecord end timestamp
legacy_uriNoonly used for legacy apps. Use channel_uuid instead when available NOTE: only visible when called from player
force_channel_nameNoonly used for legacy apps. Use channel_uuid instead when available NOTE: only visible when called from player

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only lists error codes without explaining update semantics, side effects, or required permissions. The description fails to convey whether the update is partial or full, or what happens on failure.

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 core description is very brief, but it is followed by an extensive list of error codes that could be moved to a reference. The information is front-loaded but the error list feels excessive for the description field.

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 the complexity (23 parameters, output schema exists), the description lacks necessary context such as update behavior, field interactions, and return value explanation. The error list partially compensates but does not provide operational completeness.

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 87%, so baseline is 3. The description adds no parameter-level information beyond the schema. The schema already documents most parameters adequately.

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 'Update' and the resource 'Precord' (likely a typo for 'precord'). It distinguishes the tool as updating an existing precord, but does not differentiate it from siblings like put_pvr_finished_id or put_pvr_config.

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 given on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or which sibling tool might be more appropriate for different update scenarios.

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/Nelson-PROIA/freebox-mcp'

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