Skip to content

fix: better clarify to agents how parameters should be defined #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danixeee merged 1 commit into from
Jan 8, 2026
Merged

fix: better clarify to agents how parameters should be defined #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/tools/renderItem.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,7 @@ How to use:

Guidance:
- Never submit more than one render with the same parameters, unless the user explicitly requests it.
- Template parameters must be nested under the top-level \`parameters\` object (do not place them at the top level).
- Use parameters to customize the render.
- All mandatory parameters must be provided.
- Provide values for optional parameters if it makes sense.
Expand All @@ -64,6 +65,8 @@ Guidance:
- If a parameter has a default value and the user does not provide a value, the default will be used.
- If the user is unsure about a parameter, ask for clarification rather than guessing.
- When referencing parameters in conversation, use their \`label\` or \`description\` for clarity.
Example:
- Input shape: { isDesign, projectDesignId, templateVariantId, parameters: { title: "My Title", image: "https://..." } }

Use when:
- The user wants to create a video from a specific template/variant with defined parameters.
Expand Down