langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[Enhancement/Refactor] Add optional input description #15398

New Issue
Open
opened 2026-02-21 19:21:33 -05:00 by yindo · 8 comments
yindo commented 2026-02-21 19:21:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Jul 15, 2025).

Originally assigned to: @jubinsoni on GitHub.

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Since workflows can be transformed into tools and MCP servers.
Considering that in both cases, a description of the input parameter is useful.
Considering that the Frontend app could benefit from this enhancement too...

what about adding a description field to inputs ? it could be used to automatically populate descriptions in MCP, tools, UI

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @DavideDelbianco on GitHub (Jul 15, 2025). Originally assigned to: @jubinsoni on GitHub. ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Since workflows can be transformed into tools and MCP servers. Considering that in both cases, a description of the input parameter is useful. Considering that the Frontend app could benefit from this enhancement too... what about adding a description field to inputs ? it could be used to automatically populate descriptions in MCP, tools, UI ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancementgood first issue labels 2026-02-21 19:21:33 -05:00
yindo commented 2026-02-21 19:21:33 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Jul 15, 2025):

What I meant was to have a description in the inputs Start Node:

Image

to reuse that description for workflow as tool:

Image

and MCP server config:

Image

didn't consider the description in the agent -> tool section that could use that description too

@DavideDelbianco commented on GitHub (Jul 15, 2025): What I meant was to have a description in the inputs Start Node: <img width="467" height="584" alt="Image" src="https://github.com/user-attachments/assets/858c3e68-b75d-45ca-b8a3-3d5476468241" /> to reuse that description for workflow as tool: <img width="630" height="536" alt="Image" src="https://github.com/user-attachments/assets/7348351e-e49d-490b-802f-45bed23fe9e1" /> and MCP server config: <img width="504" height="404" alt="Image" src="https://github.com/user-attachments/assets/4259004d-d18e-4497-866e-43fab701e889" /> didn't consider the description in the agent -> tool section that could use that description too
yindo commented 2026-02-21 19:21:33 -05:00
Author
Owner
Copy Link
Copy Source

@jubinsoni commented on GitHub (Jul 19, 2025):

pls review @DavideDelbianco @crazywoola
https://github.com/langgenius/dify/pull/22658

@jubinsoni commented on GitHub (Jul 19, 2025): pls review @DavideDelbianco @crazywoola https://github.com/langgenius/dify/pull/22658
yindo commented 2026-02-21 19:21:33 -05:00
Author
Owner
Copy Link
Copy Source

@jubinsoni commented on GitHub (Jul 23, 2025):

pls check once @crazywoola

@jubinsoni commented on GitHub (Jul 23, 2025): pls check once @crazywoola
yindo commented 2026-02-21 19:21:33 -05:00
Author
Owner
Copy Link
Copy Source

@jubinsoni commented on GitHub (Jul 24, 2025):

@DavideDelbianco let me know if something else is required here

@jubinsoni commented on GitHub (Jul 24, 2025): @DavideDelbianco let me know if something else is required here
yindo commented 2026-02-21 19:21:33 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Jul 25, 2025):

The purpose of having the description, is to:

  1. Show it in the front end application to help the user
  2. Use it to automatically populate description field in workflow as tool parameter description and MCP server parameter description

Before doin any more modifications, it would be wise to have the product team approval

@crazywoola

@DavideDelbianco commented on GitHub (Jul 25, 2025): The purpose of having the description, is to: 1. Show it in the front end application to help the user 2. Use it to automatically populate description field in workflow as tool parameter description and MCP server parameter description Before doin any more modifications, it would be wise to have the product team approval @crazywoola
yindo commented 2026-02-21 19:21:33 -05:00
Author
Owner
Copy Link
Copy Source

@jubinsoni commented on GitHub (Jul 25, 2025):

as suggested, added autofill logic as well to the description field @crazywoola

@jubinsoni commented on GitHub (Jul 25, 2025): as suggested, added autofill logic as well to the description field @crazywoola
yindo commented 2026-02-21 19:21:33 -05:00
Author
Owner
Copy Link
Copy Source

@jubinsoni commented on GitHub (Aug 12, 2025):

pls review @crazywoola

@jubinsoni commented on GitHub (Aug 12, 2025): pls review @crazywoola
yindo commented 2026-02-21 19:21:34 -05:00
Author
Owner
Copy Link
Copy Source

@jubinsoni commented on GitHub (Sep 1, 2025):

@crazywoola
pr already raised, anything else needs to be done here

@jubinsoni commented on GitHub (Sep 1, 2025): @crazywoola pr already raised, anything else needs to be done here
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label good first issue 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15398
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?